Loading...
Loading...
Features
Give Seology's agent a URL and it scans the page on the spot: technical, on-page, and content checks across metadata, structure, crawlability files, schema, and page-speed signals — with findings ranked by impact and the evidence to back them.
Everything the agent can verify from the page itself and its crawlability files. No invented scores — each finding points at something concrete on the page.
Title tags (commonly kept under ~60 characters to avoid truncation), meta descriptions, and Open Graph tags — present, duplicated, or missing.
H1 presence and heading hierarchy, so the page describes its own structure accurately for crawlers and readers.
Missing, duplicate, or conflicting canonical declarations that leave the preferred URL ambiguous.
Crawler directives, sitemap discoverability, and what the directives allow or block.
Structured data — present, malformed, or missing — validated for rich-result eligibility.
Images missing alt attributes or width and height dimensions, and other markup gaps.
Internal links found on the page, broken references, and anchor quality.
Render-blocking scripts, missing image dimensions, and missing lazy loading — load-harming patterns visible in the page source.
Ask in the agent chat — any public page works. No plugin, no site connection, no setup.
The agent fetches the page and its crawlability files, then checks the signals above. Findings come back ranked by impact, each with the evidence from the page.
Fixes can be applied per your execution mode — AUTOMATIC applies immediately, PLAN waits for one batch approval, APPROVE waits for each fix. With a connected GitHub repository, fixes arrive as pull requests.
After a fix or a deploy, run the scan again to confirm the page changed the way you expected.
For outcomes — rankings, clicks, impressions — pair the findings with Google Search Console or your own analytics.
Title and meta tags, heading structure, canonical tags, robots.txt, sitemap.xml, JSON-LD schema markup, image alt text, internal links, and page-speed signals such as render-blocking scripts, missing image dimensions, and missing lazy loading. Every finding includes the evidence from the page.
No. Scanning works on any public URL — you give the address to the agent and it fetches and checks the page. Connecting a GitHub repository or a Shopify store is only needed for fix delivery: repositories get fixes as pull requests, and the Shopify connector applies supported fixes to stores.
Seology doesn't publish a check count because the honest answer varies by page — what's on the page determines what gets checked. The coverage spans technical, on-page, and content checks: metadata, headings, canonicals, robots.txt, sitemap.xml, schema, images, internal links, and page-speed signals.
Issues are ranked by impact and split into those with deterministic fixes and those that need judgment. Fixes can then be applied depending on your execution mode: AUTOMATIC applies them immediately, PLAN waits for one batch approval, and APPROVE waits for your sign-off on each fix. With a connected GitHub repository, fixes arrive as pull requests.
How findings turn into reviewable pull requests.
Re-scan pages on demand after deploys and content changes.
GitHub repositories, the Shopify connector, and what's on the roadmap.
How the agent audits, proposes, and applies changes — and what it doesn't do.
One URL is all it takes — no connection, no plugin, no setup. Findings ranked by impact, with fixes a pull request away.