Loading...
Loading...
Features
Seology scans your GitHub repository for SEO issues in the code, shows which ones it can fix, and opens a GitHub pull request for each fix you ask for. You review and merge it like any other change.
Not every SEO issue has a safe code fix. The repository scan marks each issue as fixable or not, and Seology only opens pull requests for the fixable ones.
Auto-fixed via pull request
Reported for you to fix
On the scan page, paste a fine-grained GitHub token with read and write access to Contents and Pull requests, then pick a repository. The token is saved in your browser only and is sent to Seology just to call GitHub.
Seology reads up to 50 files from the default branch: HTML files, .tsx, .jsx and .js layout, page, head, _app, _document and index files, next.config, and robots.txt at the root or in public/. The scan changes nothing in your repository and uses no AI credits.
Every issue is listed with its severity, file and line. Issues with an automatic fix show an Open fix PR button. Issues without one (no h1, more than one h1, hardcoded localhost URLs) are reported so you can fix them by hand.
Click Open fix PR on one issue, or Fix all to fix every fixable issue with one pull request per file. Nothing runs until you click. The AI returns the corrected file with minimal changes: a Next.js metadata export for Next.js files, standard meta tags for HTML. If the result is unchanged or cannot be read, no pull request is opened.
Each pull request is a new seology/fix-<timestamp> branch from your default branch with one file and one commit. Fix all groups the fixes for a file into a single pull request so they cannot conflict. The description names the issue and the file, explains the change and lists what was changed.
Review the diff in GitHub as you would any other change. Seology never merges. Nothing reaches your site until you merge the pull request and deploy. Close it to discard the change. To undo a merged fix, revert the commit.
Execution modes apply to connected Shopify stores, where Seology writes changes directly to the store. Pull-request fixes are always review-first because you merge them. The Starter plan uses PLAN mode. Growth and Scale can choose any of the three. Supported Shopify fixes, such as search titles and meta descriptions on products, collections, pages and blog posts, save the previous value and can be undone for 90 days. See the Shopify integration.
The agent proposes each store fix and waits for your individual approval. Nothing is applied to the store until you sign off on it.
The agent drafts a plan with all proposed store fixes. You review the batch and approve it once, then the fixes are applied together.
The agent applies store fixes without waiting for approval and notifies you of each change so you can review it afterward.
Code fixes are delivered as GitHub pull requests. Connected Shopify stores get fixes applied directly to the store. Any public URL can be audited without a connection at all.
A connected GitHub repository is required for pull request delivery. Setup and token permissions are covered on the GitHub integration page. WordPress is audit-only: fixes are not available for WordPress sites today. See all integration options.
Seology can open a pull request for: a missing page title or Next.js metadata export, a missing meta description, img and Next.js Image tags without alt text, missing Open Graph tags in the layout, missing JSON-LD structured data, a robots.txt with no Sitemap line or with Disallow: / blocking the whole site, and poweredByHeader: true in next.config. It reports but does not fix: pages with no h1, pages with more than one h1, and hardcoded localhost URLs. The scan results show which issues have a fix before you request anything.
You run a scan, then click Open fix PR on an issue or Fix all. Each pull request is a standard GitHub pull request on its own seology/fix branch, changing one file in one commit. Fix all opens one per file. The description names the issue and the file, explains the change and lists what was changed. You review the diff and merge it to apply, or close it to discard. Seology never merges for you, so pull-request fixes are always review-first.
For pull-request fixes, nothing is applied until you merge. To undo a merged fix, revert the commit in git. Seology does not keep a separate snapshot of repository files. On connected Shopify stores, supported fixes save the previous value and can be undone from Seology for 90 days.
Scanning a repository uses no AI credits. Each fix you request uses one AI credit, charged when the fix is generated. AI credits are shared with other AI actions in your account. The Starter plan includes 30 AI credits a month, Growth includes 300 and Scale includes 1500.
Indirectly. Fixes like structured data, clear titles and descriptions, and a robots.txt that lets crawlers in and points to your sitemap make pages easier for AI search engines to retrieve and understand. Seology does not monitor or guarantee citations in AI answers. Measure that with your own sampling and analytics.
Pull-request fixes need a connected GitHub repository. Connected Shopify stores get fixes applied directly to the store. WordPress is audit-only: fixes are not available for WordPress sites today. Any public website URL can still be audited without a connection. You will not get fix delivery until a GitHub repository or Shopify store is connected.
The checks Seology runs when it audits a public URL.
Re-scan pages on demand to verify fixes and spot regressions after changes ship.
GitHub repositories, the Shopify connector, and what's on the roadmap.
How the agent audits, proposes and applies changes, and what it does not do.
Connect a repository, run a scan, and open your first fix as a pull request you can review and merge.