{"id":356709,"date":"2026-08-26T20:07:48","date_gmt":"2026-08-26T20:07:48","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/crawlsage\/"},"modified":"2026-08-26T20:07:23","modified_gmt":"2026-08-26T20:07:23","slug":"crawlsage","status":"publish","type":"plugin","link":"https:\/\/so.wordpress.org\/plugins\/crawlsage\/","author":23539515,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.0.0","stable_tag":"1.0.0","tested":"7.1","requires":"6.0","requires_php":"8.1","requires_plugins":null,"header_name":"CrawlSage","header_author":"NGOFeed","header_description":"Connect WordPress to CrawlSage for SEO audits, AI-powered recommendations, supported optimization deployment, verification, and rollback.","assets_banners_color":"201939","last_updated":"2026-08-26 20:07:23","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/crawlsage.com","header_author_uri":"https:\/\/ngofeed.com","rating":0,"author_block_rating":0,"active_installs":0,"downloads":49,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.0.0":{"tag":"1.0.0","author":"ngofeed","date":"2026-08-26 20:07:23","revision":3667754}},"upgrade_notice":{"1.0.0":"<p>Initial WordPress.org release of CrawlSage.<\/p>"},"ratings":[],"assets_icons":{"icon.svg":{"filename":"icon.svg","revision":3667753,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3667753,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3667753,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3667753,"resolution":"1","location":"assets","locale":"","width":2940,"height":1912},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3667753,"resolution":"2","location":"assets","locale":"","width":2940,"height":1912},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3667753,"resolution":"3","location":"assets","locale":"","width":2940,"height":1912},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3667753,"resolution":"4","location":"assets","locale":"","width":2940,"height":1912},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3667753,"resolution":"5","location":"assets","locale":"","width":2940,"height":1912}},"screenshots":{"1":"CrawlSage dashboard with SEO health, audit status, recommendations, and website overview.","2":"Select WordPress content and start a cloud-powered SEO audit.","3":"Follow live crawl and SEO audit progress directly inside WordPress.","4":"Review AI-powered SEO recommendations before deployment.","5":"Deploy approved SEO optimizations directly to WordPress and track applied changes."}},"plugin_section":[],"plugin_tags":[2994,186,31034,167235,475],"plugin_category":[55],"plugin_contributors":[277720],"plugin_business_model":[],"class_list":["post-356709","plugin","type-plugin","status-publish","hentry","plugin_tags-metadata","plugin_tags-seo","plugin_tags-seo-audit","plugin_tags-technical-seo","plugin_tags-wordpress-seo","plugin_category-seo-and-marketing","plugin_contributors-ngofeed","plugin_committers-ngofeed"],"banners":{"banner":"https:\/\/ps.w.org\/crawlsage\/assets\/banner-772x250.png?rev=3667753","banner_2x":"https:\/\/ps.w.org\/crawlsage\/assets\/banner-1544x500.png?rev=3667753","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/crawlsage\/assets\/icon.svg?rev=3667753","icon":"https:\/\/ps.w.org\/crawlsage\/assets\/icon.svg?rev=3667753","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/crawlsage\/assets\/screenshot-1.png?rev=3667753","caption":"CrawlSage dashboard with SEO health, audit status, recommendations, and website overview."},{"src":"https:\/\/ps.w.org\/crawlsage\/assets\/screenshot-2.png?rev=3667753","caption":"Select WordPress content and start a cloud-powered SEO audit."},{"src":"https:\/\/ps.w.org\/crawlsage\/assets\/screenshot-3.png?rev=3667753","caption":"Follow live crawl and SEO audit progress directly inside WordPress."},{"src":"https:\/\/ps.w.org\/crawlsage\/assets\/screenshot-4.png?rev=3667753","caption":"Review AI-powered SEO recommendations before deployment."},{"src":"https:\/\/ps.w.org\/crawlsage\/assets\/screenshot-5.png?rev=3667753","caption":"Deploy approved SEO optimizations directly to WordPress and track applied changes."}],"raw_content":"<!--section=description-->\n<p>CrawlSage helps you discover SEO issues across your WordPress website, review actionable recommendations, apply supported optimizations, and track what changed.<\/p>\n\n<p>Connect your WordPress website to your CrawlSage account and manage the SEO workflow from discovery through deployment.<\/p>\n\n<h4>What can CrawlSage do?<\/h4>\n\n<p>CrawlSage supports:<\/p>\n\n<ul>\n<li>Discovering WordPress URLs and supported content types.<\/li>\n<li>Running SEO audits for supported pages and content.<\/li>\n<li>Identifying technical and on-page SEO issues.<\/li>\n<li>Reviewing SEO recommendations before making changes.<\/li>\n<li>Optimizing SEO titles and meta descriptions.<\/li>\n<li>Managing focus keyword recommendations.<\/li>\n<li>Reviewing and applying image alt text recommendations.<\/li>\n<li>Tracking applied fixes and deployment history.<\/li>\n<li>Verifying supported changes after deployment.<\/li>\n<li>Rolling back supported optimizations.<\/li>\n<li>Viewing connection and diagnostic information.<\/li>\n<\/ul>\n\n<p>CrawlSage does not automatically apply SEO changes without an authorized workflow. Supported changes are reviewed and authorized by a WordPress administrator before deployment.<\/p>\n\n<p>A CrawlSage account and connection to the CrawlSage service are required to use cloud-powered features.<\/p>\n\n<h4>How it works<\/h4>\n\n<ol>\n<li>Connect your WordPress website to CrawlSage.<\/li>\n<li>Discover the URLs and supported content on your website.<\/li>\n<li>Run an SEO audit.<\/li>\n<li>Review detected issues and recommendations.<\/li>\n<li>Approve the optimizations you want to apply.<\/li>\n<li>Deploy supported changes to WordPress.<\/li>\n<li>Verify the result and review fix history.<\/li>\n<li>Roll back supported changes when necessary.<\/li>\n<\/ol>\n\n<h4>Secure connection<\/h4>\n\n<p>CrawlSage uses an OAuth connection. The administrator is redirected to the CrawlSage app to authenticate. The browser receives only a short-lived authorization code and state value. WordPress exchanges the authorization code directly with the CrawlSage API.<\/p>\n\n<p>Long-lived authentication tokens are not transported through browser URLs.<\/p>\n\n<p>Authenticated credentials stored by the plugin are protected using the plugin's credential storage mechanism and WordPress security keys.<\/p>\n\n<h3>External services<\/h3>\n\n<p>CrawlSage is a SaaS-connected plugin and requires communication with the CrawlSage service.<\/p>\n\n<p>API service:<\/p>\n\n<p>https:\/\/api.crawlsage.com<\/p>\n\n<p>Web application:<\/p>\n\n<p>https:\/\/app.crawlsage.com<\/p>\n\n<p>A CrawlSage account is required to use the connected SEO audit, recommendation, deployment, verification, credit, and account features.<\/p>\n\n<h4>Connection data<\/h4>\n\n<p>When an administrator starts or completes a CrawlSage connection, the plugin may send:<\/p>\n\n<ul>\n<li>Site URL and hostname.<\/li>\n<li>WordPress version.<\/li>\n<li>PHP version.<\/li>\n<li>CrawlSage plugin version.<\/li>\n<li>WordPress timezone.<\/li>\n<li>CrawlSage site or installation identifier.<\/li>\n<li>Administrator email when supplied as part of the connection workflow.<\/li>\n<li>OAuth authorization code and state during the connection workflow.<\/li>\n<\/ul>\n\n<p>This information is used to authenticate and associate the WordPress website with the appropriate CrawlSage account.<\/p>\n\n<h4>Discovery and audit data<\/h4>\n\n<p>When an administrator performs discovery or starts an audit, the plugin may send information required to analyze supported WordPress content, including:<\/p>\n\n<ul>\n<li>Page and content URLs.<\/li>\n<li>WordPress object IDs and object types.<\/li>\n<li>Content and URL inventory metadata.<\/li>\n<li>Indexability and editability information.<\/li>\n<li>SEO titles and meta descriptions.<\/li>\n<li>Focus keyword information.<\/li>\n<li>Heading information.<\/li>\n<li>Canonical and robots information.<\/li>\n<li>Structured-data information where supported.<\/li>\n<li>Image and alt-text metadata.<\/li>\n<li>Audit results and detected SEO issues.<\/li>\n<li>Relevant timestamps and processing status.<\/li>\n<\/ul>\n\n<p>This information is used to discover content, evaluate supported SEO issues, and produce audit results.<\/p>\n\n<h4>Recommendation data<\/h4>\n\n<p>When recommendations are generated or retrieved, CrawlSage may process:<\/p>\n\n<ul>\n<li>Issue identifiers.<\/li>\n<li>Affected URLs and WordPress objects.<\/li>\n<li>Existing SEO values.<\/li>\n<li>Recommended values.<\/li>\n<li>Priority and confidence information.<\/li>\n<li>Related audit metadata.<\/li>\n<\/ul>\n\n<p>This information is used to generate and manage SEO recommendations.<\/p>\n\n<h4>Deployment, verification, and rollback data<\/h4>\n\n<p>When an administrator applies, verifies, or rolls back a supported optimization, the plugin may send:<\/p>\n\n<ul>\n<li>Recommendation or fix identifiers.<\/li>\n<li>Target WordPress object information.<\/li>\n<li>Selected or applied values.<\/li>\n<li>Previous values where required for verification or rollback.<\/li>\n<li>Operation status.<\/li>\n<li>Relevant timestamps.<\/li>\n<li>Error information required to diagnose a failed operation.<\/li>\n<\/ul>\n\n<p>This information is used to apply authorized changes, verify their status, maintain fix history, and support rollback.<\/p>\n\n<h4>Credits and account status<\/h4>\n\n<p>When CrawlSage needs current account or usage information, the plugin may send the authenticated site\/account identifier and request information such as:<\/p>\n\n<ul>\n<li>Available credits.<\/li>\n<li>Plan status.<\/li>\n<li>Usage eligibility.<\/li>\n<\/ul>\n\n<p>Payment-card and payment-processing details are not stored by this WordPress plugin.<\/p>\n\n<h4>When data is sent<\/h4>\n\n<p>The plugin does not initiate CrawlSage service requests before an administrator starts the connection process.<\/p>\n\n<p>After connection, requests may occur when an administrator uses CrawlSage features or when an enabled CrawlSage background process performs a connected synchronization or status operation.<\/p>\n\n<p>The plugin does not send WordPress passwords to CrawlSage.<\/p>\n\n<p>CrawlSage does not use an external executable-code update system for this plugin. Plugin updates distributed through WordPress.org use the standard WordPress.org plugin update mechanism.<\/p>\n\n<p>CrawlSage processes transmitted information according to its privacy and data-retention practices.<\/p>\n\n<p>Privacy Policy:\nhttps:\/\/crawlsage.com\/legal\/privacy-policy<\/p>\n\n<p>Terms of Service:\nhttps:\/\/crawlsage.com\/legal\/terms-of-service<\/p>\n\n<h3>Data handling<\/h3>\n\n<p>The plugin stores connection state and authenticated credentials in WordPress options.<\/p>\n\n<p>Operational information related to discovered URLs, audits, fixes, history, and diagnostics may be stored in CrawlSage custom database tables.<\/p>\n\n<p>Sensitive authentication credentials are stored using CrawlSage's protected credential-storage mechanism.<\/p>\n\n<h4>Deactivation<\/h4>\n\n<p>Deactivating CrawlSage:<\/p>\n\n<ul>\n<li>Preserves plugin settings and operational data.<\/li>\n<li>Preserves the existing connection so the plugin can resume after reactivation.<\/li>\n<li>Removes or clears CrawlSage scheduled events as required by the plugin lifecycle.<\/li>\n<\/ul>\n\n<h4>Uninstall<\/h4>\n\n<p>When CrawlSage is uninstalled:<\/p>\n\n<ul>\n<li>Authentication credentials are removed.<\/li>\n<li>Connection settings are removed.<\/li>\n<li>Security-related transients are removed.<\/li>\n<li>CrawlSage plugin options are removed.<\/li>\n<\/ul>\n\n<p>CrawlSage custom database tables are retained by default.<\/p>\n\n<p>If <strong>Delete CrawlSage data on uninstall<\/strong> is enabled before uninstalling the plugin, CrawlSage custom database tables are also removed.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Upload or install CrawlSage from the WordPress Plugins screen.<\/li>\n<li>Activate <strong>CrawlSage<\/strong>.<\/li>\n<li>Open <strong>CrawlSage<\/strong> from WordPress Admin.<\/li>\n<li>Select <strong>Connect with CrawlSage<\/strong>.<\/li>\n<li>Sign in to your CrawlSage account and authorize the connection.<\/li>\n<li>After the connection is verified, open the CrawlSage dashboard and begin discovering or auditing your website.<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"do%20i%20need%20a%20crawlsage%20account%3F\"><h3>Do I need a CrawlSage account?<\/h3><\/dt>\n<dd><p>Yes. A CrawlSage account is required to use the connected CrawlSage service and cloud-powered SEO features.<\/p><\/dd>\n<dt id=\"does%20crawlsage%20automatically%20change%20my%20website%3F\"><h3>Does CrawlSage automatically change my website?<\/h3><\/dt>\n<dd><p>Supported SEO changes are applied through an authorized workflow. Administrators can review recommendations before applying supported optimizations.<\/p><\/dd>\n<dt id=\"how%20does%20automatic%20connection%20work%3F\"><h3>How does automatic connection work?<\/h3><\/dt>\n<dd><p>CrawlSage opens the CrawlSage web application for authentication. The browser returns a short-lived authorization code and state value. WordPress then exchanges that authorization code directly with the CrawlSage API.<\/p>\n\n<p>Long-lived authentication tokens are not sent through browser URLs.<\/p><\/dd>\n<dt id=\"does%20crawlsage%20send%20data%20before%20i%20connect%20my%20website%3F\"><h3>Does CrawlSage send data before I connect my website?<\/h3><\/dt>\n<dd><p>The plugin does not initiate CrawlSage service requests before an administrator starts the connection process.<\/p><\/dd>\n<dt id=\"what%20seo%20optimizations%20are%20supported%3F\"><h3>What SEO optimizations are supported?<\/h3><\/dt>\n<dd><p>Depending on the detected issue and supported WordPress configuration, CrawlSage can provide workflows for SEO titles, meta descriptions, focus keywords, image alt text, and other supported SEO audit recommendations.<\/p><\/dd>\n<dt id=\"can%20i%20review%20a%20recommendation%20before%20applying%20it%3F\"><h3>Can I review a recommendation before applying it?<\/h3><\/dt>\n<dd><p>Yes. CrawlSage is designed around a review and authorization workflow for supported optimizations.<\/p><\/dd>\n<dt id=\"can%20crawlsage%20roll%20back%20changes%3F\"><h3>Can CrawlSage roll back changes?<\/h3><\/dt>\n<dd><p>CrawlSage maintains fix history for supported deployments and can roll back supported changes when rollback information is available and the current WordPress state permits it.<\/p><\/dd>\n<dt id=\"does%20crawlsage%20store%20my%20wordpress%20password%3F\"><h3>Does CrawlSage store my WordPress password?<\/h3><\/dt>\n<dd><p>No. CrawlSage does not require or transmit your WordPress account password.<\/p><\/dd>\n<dt id=\"does%20crawlsage%20store%20payment%20information%20in%20wordpress%3F\"><h3>Does CrawlSage store payment information in WordPress?<\/h3><\/dt>\n<dd><p>No. Payment processing and billing are handled by the CrawlSage service. Payment-card details are not stored by this WordPress plugin.<\/p><\/dd>\n<dt id=\"what%20happens%20when%20i%20deactivate%20crawlsage%3F\"><h3>What happens when I deactivate CrawlSage?<\/h3><\/dt>\n<dd><p>Plugin data and connection information are preserved so CrawlSage can resume after reactivation. Scheduled CrawlSage events are cleared according to the plugin lifecycle.<\/p><\/dd>\n<dt id=\"what%20happens%20when%20i%20uninstall%20crawlsage%3F\"><h3>What happens when I uninstall CrawlSage?<\/h3><\/dt>\n<dd><p>Plugin credentials, settings, security transients, and options are removed.<\/p>\n\n<p>CrawlSage custom tables are retained by default unless <strong>Delete CrawlSage data on uninstall<\/strong> is enabled before uninstalling.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>Initial WordPress.org release of CrawlSage.<\/li>\n<li>Added secure automatic and manual CrawlSage account connection.<\/li>\n<li>Added WordPress URL discovery and SEO audit workflows.<\/li>\n<li>Added SEO recommendation review and supported deployment workflows.<\/li>\n<li>Added SEO title, meta description, focus keyword, and image alt text optimization support.<\/li>\n<li>Added deployment verification, fix history, and supported rollback.<\/li>\n<li>Added encrypted credential storage and secure authentication handling.<\/li>\n<li>Added diagnostics and connection health information.<\/li>\n<\/ul>","raw_excerpt":"Connect WordPress to CrawlSage for SEO audits, AI-powered recommendations, supported optimization deployment, verification, and rollback.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/so.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/356709","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/so.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/so.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/so.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=356709"}],"author":[{"embeddable":true,"href":"https:\/\/so.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/ngofeed"}],"wp:attachment":[{"href":"https:\/\/so.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=356709"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/so.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=356709"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/so.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=356709"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/so.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=356709"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/so.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=356709"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/so.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=356709"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}