Simple outside. Rigorous underneath.
From website address to prioritised repair plan
Cozmo does not spray generic advice at every page. It first establishes the crawl boundary, captures the evidence it can genuinely observe, and then applies only the relevant rules. A check that is not applicable, unavailable or unsupported should not become a pretend fault.
Start to finish
The complete ScanMySEO inspection route
Each stage narrows uncertainty before the next stage adds interpretation.
- 01Set the scope
Enter a public website you are authorised to analyse and, optionally, its sitemap.
- 02Confirm access
Sign in, confirm the email and optionally personalise how findings are ordered and explained.
- 03Reserve capacity
The exact included or PAYG allowance is reserved and the page cap becomes the crawl boundary.
- 04Discover pages
Cozmo uses the start URL, internal links, sitemap evidence and supported robots instructions.
- 05Capture evidence
Eligible pages are fetched and, where needed, rendered; final responses and page signals are recorded.
- 06Run core rules
The 34 report families turn supported evidence into page and site-wide findings.
- 07AI Enhanced Audit
Paid access reviews eligible page evidence against applicable checks from the 88-check matrix.
- 08Ask Cozmo
Paid users turn the completed report into priorities, summaries and developer-ready tasks.
- 09Implement & re-crawl
You review and apply changes outside ScanMySEO, then run a new crawl to measure movement.
Before a finding exists
What Cozmo records and compares
These observations give the rules something concrete to work from. Availability varies by page, depth, response and crawl conditions.
Included crawl intelligence
All 34 core finding families
These are the deterministic report families generated from captured crawl evidence. Some checks are page-level, some are site-wide, and some run only when the page depth, evidence or site context makes the check meaningful.
Page meaning & metadataSignals that tell visitors and search systems what each page is, what it promises and how it is organised. 7 families
Page title qualityTitle Issues Core
Checks captured title tags for missing values, duplication and weak length or clarity patterns that make pages difficult to distinguish.
- Evidence used
- The final page title recorded for each eligible page and comparisons across the captured crawl.
Meta description qualityDescription Issues Core
Checks whether descriptions are missing, duplicated or poorly sized for a useful search-result summary.
- Evidence used
- Captured meta descriptions and site-wide comparisons across the crawl.
Heading structureHeading Issues Core
Checks for missing or confusing H1 and heading structures so the page has a clear, scannable hierarchy.
- Evidence used
- H1, H2 and H3 text extracted from the captured page.
Image alternative textImage Alt Issues Core
Checks sampled images for missing, empty, very short, overly long, non-descriptive or keyword-stuffed alternative text.
- Evidence used
- Image source and alt attributes captured from eligible page markup.
Structured data completenessStructured Data Issues Core
Checks captured JSON-LD and supported schema types for missing expected properties or other reportable validation problems.
- Evidence used
- Structured-data objects found in the page source; malformed or unavailable evidence may limit the result.
Breadcrumb navigationBreadcrumb Issues Core
Checks visible breadcrumbs and BreadcrumbList data for missing navigation, labels, links or required item properties.
- Evidence used
- HTML breadcrumb patterns, linked destinations and captured BreadcrumbList markup.
URL quality and normalisationURL Issues Core
Checks non-tracking query parameters, lowercase consistency, spaces and other URL patterns that can create unclear variants.
- Evidence used
- The requested and final URL, parsed path, query string and normalisation signals.
Content quality & trustSignals that help a visitor understand the page, trust its source and avoid thin, repeated or stale information. 6 families
Content sufficiencyContent Issues Core
Checks whether the captured main content is unusually sparse or otherwise triggers a supported content-quality rule.
- Evidence used
- Visible main-content text, word count and page-level content signals.
Duplicate and near-duplicate contentDuplicate Content Issues Core
Compares captured page content to identify repeated or highly similar pages that may compete or add little unique value.
- Evidence used
- Normalised visible content, content hashes and similarity comparisons within the captured crawl.
ReadabilityReadability Issues Core
Calculates a readability signal and flags copy that may be difficult for its intended audience to follow.
- Evidence used
- A bounded sample of visible page text; results are a planning aid, not a judgement of subject expertise.
Content freshness signalsContent Freshness Issues Core
Looks for available age or update evidence and flags stale-looking content where the captured signals support it.
- Evidence used
- Visible date language and response metadata such as Last-Modified where it is available and usable.
Text-to-HTML balanceText-to-HTML Ratio Issues Core
Compares visible text with captured markup to highlight pages where useful content may be buried in disproportionately heavy HTML.
- Evidence used
- Lengths of cleaned HTML and extracted visible main content.
Visible E-E-A-T and trust signalsE_E_A_T_ISSUES Core
Checks for surface-level authorship, organisation, contact, privacy, disclaimer, update and authoritative-reference signals.
- Evidence used
- Captured metadata, visible labels, links and supported structured-data evidence. It does not certify expertise or trustworthiness.
Discovery, indexing & architectureSignals that determine whether important pages can be found, interpreted and connected without mixed instructions. 8 families
Canonical signalsCanonical Issues Core
Checks canonical tags for missing, invalid or conflicting preferred-URL instructions supported by the captured page.
- Evidence used
- Canonical link markup, the requested URL and the final resolved URL.
International targetingHreflang Issues Core
Validates hreflang values and destinations. Missing hreflang is only treated as relevant when the captured site appears multilingual or multi-regional.
- Evidence used
- Alternate-language link tags, destination checks and page-language signals across the crawl.
Noindex directivesNoindex Issues Core
Surfaces global and supported user-agent-specific noindex instructions so important public pages are not hidden accidentally.
- Evidence used
- Robots meta and supported noindex directives captured from eligible pages.
Orphan and potentially orphaned pagesOrphan Pages Core
Compares crawl discovery, internal links and sitemap evidence to find pages with weak or absent internal pathways, while respecting incomplete-scope warnings.
- Evidence used
- Visited URLs, sitemap URLs, incoming internal links and whether the crawl scope was complete.
Sitemap-listed pages not successfully reachedMissing Sitemap Pages Core
Checks a bounded sample of sitemap URLs that were not successfully crawled and separates reachable omissions from truly inaccessible entries.
- Evidence used
- Sitemap discovery, crawl results and bounded availability checks for uncrawled URLs.
Click depthLink Depth Issues Core
Flags useful pages buried too many internal steps from the starting page, where depth evidence is available.
- Evidence used
- The crawl depth recorded when each eligible page was discovered.
Internal linking strengthInternal Linking Issues Core
Checks incoming internal-link counts and related signals to find pages that receive too little navigational support.
- Evidence used
- Normalised internal links, source pages, anchor text and incoming-link counts.
Primary navigation healthNavigation Issues Core
Reviews captured navigation links for supported structural problems, including unusually crowded navigation.
- Evidence used
- Links present inside visible nav elements in the captured markup.
Links & redirectsSignals that keep visitors and crawlers moving to the intended destination without dead ends or avoidable detours. 3 families
Broken or potentially inaccessible linksPotentially Inaccessible Links Core
Checks unique internal and relevant external targets for errors, redirects and destinations that need manual confirmation when a security layer blocks verification.
- Evidence used
- Source URL, target URL, status, final URL, redirect chain and bot-protection or rate-limit context.
Page-level redirect behaviourRedirect Issues Core
Checks acquired redirect chains for unexpected hops, error states or final destinations that create ambiguity.
- Evidence used
- The redirect chain and final response recorded during acquisition.
Excessive redirect useExcessive Redirects Core
Looks across the crawl for redirect concentration or chains that add avoidable latency and maintenance risk.
- Evidence used
- Page-level redirect chains aggregated across the captured scope.
Security & transportNon-invasive website safety indicators. These checks do not exploit vulnerabilities or certify compliance. 2 families
HTTPS and certificate basicsHTTPS Issues Core
Checks whether a page uses HTTPS and whether basic certificate evidence indicates an expiry or connection problem.
- Evidence used
- Final URL scheme and bounded TLS certificate inspection where the host permits it.
Response security headersSecurity Headers Issues Core
Aggregates supported response-header controls across captured pages and reports missing or weak controls as advisory findings.
- Evidence used
- Final response headers, status, request method, coverage and verification warnings. Absence is not inferred from a challenge page.
Performance & code weightSignals that reveal slow responses, heavy assets and front-end weight that can delay useful content. 6 families
Oversized image evidenceOversized Images Core
Reports oversized-image evidence where a reliable size signal was captured; unavailable size evidence is not treated as a failure.
- Evidence used
- Image metadata and available transfer-size observations from the crawl.
Response and page performancePerformance Issues Core
Checks supported timing and transfer signals such as time to first byte, navigation duration, total transferred page weight and large resources.
- Evidence used
- Final response timing plus browser navigation and resource timing where the check ran.
Lab Core Web Vitals signalsCORE_WEB_VITALS Core
Captures lab Largest Contentful Paint and Cumulative Layout Shift when browser evidence is available. Real-user interaction metrics are not invented.
- Evidence used
- Browser performance observations from the rendered page; FID is unavailable without real interaction and remains unset.
CSS weight and deliveryCSS Usage Issues Core
Checks supported stylesheet counts, sizes or delivery patterns on pages where the bounded CSS analysis runs.
- Evidence used
- Linked and inline stylesheet evidence captured for eligible shallower pages.
JavaScript weight and deliveryJavaScript Usage Issues Core
Checks supported script counts, sizes or delivery patterns on pages where the bounded JavaScript analysis runs.
- Evidence used
- Linked and inline script evidence captured for eligible shallower pages.
Third-party script pressureSlow Third-Party Scripts Core
Identifies sampled third-party resources whose observed duration may be slowing the page.
- Evidence used
- Browser resource timing for external scripts, bounded to the data retained for the report.
Mobile & visitor experienceBasic experience checks that help people reach and read the page on common devices without unnecessary obstruction. 2 families
Mobile foundationsMobile-Friendly Issues Core
Checks for a usable viewport declaration and other supported mobile blockers such as obsolete Flash content.
- Evidence used
- Viewport metadata and captured page elements.
Intrusive pop-upsPopup Issues Core
Looks for captured dialog, overlay or pop-up patterns that may obstruct the main content.
- Evidence used
- Visible markup patterns in the acquired page. Behaviour that appears only after unobserved interaction may require manual review.
Premium step after the report
Ask Cozmo turns findings into a work order
Ask Cozmo works from the completed report context. Instead of forcing a mechanic, gardener, founder or developer through every row, it can reorganise the same evidence into the decision format that person needs.
- “What should I fix first this week?”
- “Turn the technical findings into developer tasks.”
- “Explain the mobile problems without SEO jargon.”
- “Which pages need content work first?”
- “Create a client-ready summary from this crawl.”
It does not browse, upload files, log into the website, change settings or execute backend actions unless a future feature is explicitly identified.
Compare paid accessEvidence becomes action
Where the checks appear
Outputs vary by entitlement and available evidence, but they share the same completed crawl record.
Dashboard
Website health, scope, priority groups, affected pages, history and the next action.
A shareable explanation of the audit, top actions and supported AI findings where included.
CSV / workbook
Page inventory, issue rows, owners, statuses, evidence and implementation-ready worksheets according to entitlement.
AI action plans
Paid AI summaries, page plans, category roll-ups and accepted findings where the premium run completes.
Ask Cozmo
Report-specific questions, plain-English summaries, stakeholder views and developer task formats.
What the numbers do—and do not—mean
Accuracy, scope and honest limitations
Cozmo is designed for eligible public HTTP and HTTPS content. It does not intentionally enter login-only, private or gated areas or bypass access controls.
Page caps, crawl limits, target-site blocks, rendering conditions, timeouts and incomplete scope can reduce coverage. Read every report with its page count and warnings.
A missing warning means the captured evidence did not produce that finding. It does not certify the page, guarantee rankings or replace specialist review.
Lab LCP and CLS may be captured. Interaction metrics that require real users are not guessed, and field data should be checked separately where needed.
Security checks inspect available transport and header indicators. They do not exploit vulnerabilities, prove an attack or certify compliance.
AI output can be partial, wrong or incomplete. Verify claims, test recommendations and keep human approval final.
ScanMySEO does not log into your CMS, publish content, deploy code or change settings. Backups, implementation, testing and rollback stay with you.
A later crawl may differ in scope, page count, site content, entitlement, methodology or available evidence—not only because the website changed.
Questions people ask before scanning
Complete audit checklist FAQ
Does every check run on every page?
No. This page is the complete available catalogue. Page type, evidence, crawl depth, site context, technical access, page cap and entitlement determine what is applicable. ScanMySEO should not create a finding simply because a check exists.
What is included before the paid AI layer?
The crawl captures supported technical, content, link, performance, mobile, security and architecture evidence and maps it into the 34 core report families. The saved dashboard and available exports depend on the current plan or order.
What do paid users unlock?
Where enabled and entitled, paid plans and eligible PAYG audits add AI Enhanced Audit and Ask Cozmo. AI Enhanced Audit reviews eligible page evidence; Ask Cozmo turns the completed report into understandable priorities, summaries and tasks.
Do all 88 premium AI checks run on every page?
No. The matrix contains 88 possible review questions. ScanMySEO selects a bounded, page-appropriate subset and accepts only validated, evidence-grounded findings. A contact page, product page and legal page should not receive identical review logic.
Can the AI verify live prices, stock or the latest market?
Not by browsing in the current AI Enhanced Audit. It can flag stale-looking or inconsistent evidence inside the captured page, but live prices, product availability and current market claims require a separate check against current authoritative sources.
Why does this page no longer claim FID is measured?
First Input Delay requires genuine user interaction. The lab crawler can capture LCP and CLS when browser evidence is available, but it keeps FID unavailable rather than manufacturing a value.
Does noindex stop a page being audited?
Noindex is an indexing instruction, not an access control. A publicly accessible page may still be analysed so you can review whether the directive is intentional. Robots and access restrictions are treated separately.
Can ScanMySEO fix the website automatically?
No. The product provides analysis, evidence and recommendations. You or your authorised team decide what to implement, test and deploy, then re-crawl to measure the result.
Start with the address you already know
Run the diagnostic. Get the job sheet.
Begin with the free core audit, then use paid AI Enhanced Audit and Ask Cozmo when you need deeper page intelligence and faster hand-off.