Loading...
Loading...
Features
Seology has two real integrations — GitHub repositories for pull-request fixes and a Shopify connector for stores — plus URL scanning that works on any public site with no connection at all. WordPress and other CMS connectors are on the roadmap, and we'd rather say that than pretend they exist.
The primary integration. Connect a repository, the agent scans your site's code and pages, and every fix arrives as a pull request that goes through your normal code review and deploy process — not around it.
An OAuth connector for stores. Connect your shop, the agent audits its pages and content, and applies supported fixes according to your execution mode — with a 90-day rollback window on applied fixes.
Not technically an integration, and that's the point: give the agent a URL in the chat and it scans the page — meta tags, headings, robots.txt, sitemap.xml, schema markup, and page-speed signals. Scanning works on every public site, including platforms that don't have a connector yet.
Authenticate with GitHub and choose the repository your site lives in. Seology only sees what that connection grants — it never gets your CMS or hosting credentials.
Seology reads the code and pages associated with the repo and runs its technical, on-page, and content checks — meta tags, headings, robots.txt, sitemap.xml, schema markup, and page-speed signals.
Issues are categorized by severity and by whether they have a deterministic fix. You see what's broken, why it matters, and what the agent proposes to do about it.
Each fix arrives as a PR with a plain-English explanation of the issue and the change. Review the diff, merge to apply, or close to discard — your normal review workflow, unchanged.
Next.js, Astro, plain HTML — if it lives in a GitHub repo, the agent can open pull requests against it.
GitHub authentication uses OAuth. Seology never sees your site's admin password or CMS credentials.
Merged changes can be reverted in git, and applied fixes keep a 90-day rollback window.
These connectors are planned but not available in self-service setup today. Rather than document them as if they existed, here's the honest state — and what works in the meantime.
A WordPress connector is planned. Today: WordPress URLs scan like any other site, so audits and findings work — automatic fix delivery does not.
Connectors for additional platforms such as Webflow, Wix, and Squarespace are on the roadmap. Their public URLs can be scanned now.
Building on a platform without a connector yet? If the site's source is in a GitHub repository, the repository integration gives you pull-request fix delivery today.
Two: GitHub and Shopify. GitHub is the primary integration — connect a repository and Seology scans your site's code, finds SEO issues, and delivers fixes as pull requests that go through your normal review. Shopify connects via OAuth for stores. Beyond those, any public website URL can be scanned without a connection at all.
You connect a repository, Seology reads the code and pages associated with it, and runs its technical, on-page, and content checks — meta tags, headings, robots.txt, sitemap.xml, schema markup, and page-speed signals. When the agent finds something it can fix, it opens a pull request with a plain-English explanation. You review the diff, merge or close it, and deploy as usual.
Not yet. A WordPress connector is on the roadmap, but it is not available in self-service setup today. What works right now: WordPress URLs can be scanned like any other website, so you still get audits and findings — you just don't get automatic fix delivery until a connector or a repository path exists for the site.
Connectors for additional platforms are on the roadmap and not available today. Any public site — including Webflow, Wix, and Squarespace — can still be scanned by URL. If the site's source lives in a GitHub repository, the repository integration gives you pull-request fix delivery for it.
Yes. Applied fixes store a before-state snapshot and keep a 90-day rollback window. Repository fixes can also be undone with a standard git revert after merge. Test the rollback path on a safe example before enabling large batches.
The technical, on-page, and content checks Seology runs on every scan.
How the agent turns findings into reviewable pull requests.
Re-scan pages on demand after deploys and content changes.
How the agent audits, proposes, and applies changes — and what it doesn't do.
Scan any URL right now, connect a GitHub repository for pull-request fixes, or connect a Shopify store. Everything else — honestly — is on the roadmap.