PageRanking.io
Free website audit
Skip to content

PageRanking.io guide

Operate autonomous search growth safely

Connect a website, verify brand evidence, run an audit, and let governed agents prioritize SEO, AEO and GEO work. Low-risk changes can run automatically; higher-risk work follows your approval policy. Every connector deployment keeps a before snapshot for rollback.

Production workflow

  1. Connect WordPress, WooCommerce, Shopify, Webflow or a custom website.
  2. Run Search Intelligence and verify business facts in Brand Intelligence.
  3. Create evidence-grounded authority content and review it before publishing.
  4. Use Operations to inspect provider readiness, scheduled runs, retries and notifications.
  5. Review Conversions to prioritize work by business impact.

Audit access versus publishing access

A public URL is enough for a read-only audit. PageRanking requests publishing credentials only when you choose to apply a supported change. Approval mode keeps every proposed write waiting for you; autopilot applies only eligible actions allowed by your saved policy.

ConnectorReadsWritesVerification and rollback
WordPressPages and editable fieldsTitle, excerpt, contentRequired read-back; field snapshot
WooCommerceProducts and editable fieldsName and descriptionsRequired read-back; product-field snapshot
ShopifySupported Online Store pagesTitle and bodyRequired read-back; page-field snapshot
WebflowSupported pages and collection contentSupported text fieldsPublish then read-back; field snapshot
Custom websiteAdapter-reported pagesAdapter-reported fieldsRequired adapter read-back and rollback capability

Current limitation: schema and theme-level writes are not implied by these connectors. The Websites screen reports the exact capability exposed by the selected connection.

Connector setup and revocation

WordPress
  1. Create a dedicated WordPress Application Password for the PageRanking user.
  2. Enter the username and Application Password in Websites; never enter the normal account password.
  3. Run the read-only connection check. A protected write is certified only after the first approved write and read-back.
  4. Revoke the Application Password in WordPress and select Disconnect in PageRanking to stop future jobs.
Shopify
  1. Create or authorize an Admin API integration with only the supported content scopes.
  2. Connect the store in Websites and run the read-only permission check.
  3. PageRanking stores a field snapshot before a write and compares the returned page with the approved value.
  4. Revoke the app token in Shopify and disconnect it in PageRanking when access is no longer required.
Webflow
  1. Create a restricted site token for the intended Webflow site.
  2. Connect it in Websites and confirm the discovered site or collection content.
  3. A publish response remains verification-pending until PageRanking reads the intended value back.
  4. Revoke the token in Webflow and disconnect it in PageRanking to stop queued writes.

WooCommerce connection

  1. In WordPress, open WooCommerce → Settings → Advanced → REST API.
  2. Create a key for the store owner with Read/Write permission.
  3. Choose WooCommerce in PageRanking and enter the ck_ consumer key and cs_ consumer secret.
  4. After verification, use Websites to discover products and review a protected change before publishing.
  5. To revoke access, delete the REST API key in WooCommerce and select Disconnect in PageRanking.

Custom website connector

  1. Ask the hosting or development owner to open the PageRanking adapter specification from the dashboard.
  2. Install a server-side HTTPS endpoint that supports page discovery, controlled updates and rollback.
  3. Create a unique shared secret of at least 24 characters and enter it only in the encrypted PageRanking connection form.
  4. Run the handshake. PageRanking will reject the connection unless read, write and rollback capabilities are verified.

There is no universal password-free installation for arbitrary custom code. The one-time adapter must be installed by someone who controls the source or hosting account; the business owner does not need to edit code or share their normal password.

Five-minute first value

  1. Add your business and public website URL.
  2. Confirm the detected platform or choose the correct one.
  3. Run the first read-only audit; no publishing credential is required.
  4. Open Opportunities and inspect the URL, evidence, and recommendation.
  5. If you want to publish, connect the least-privilege credential, keep Approval mode enabled, and review the exact change before authorizing it.

Operational controls

The scheduler accepts a protected server-to-server trigger and records every run. Mutation endpoints are rate-limited, raw IP addresses are never stored, and alerts are written to the in-app inbox. Email delivery follows each customer’s notification settings.

Return to workspace · Privacy · Terms