Start with high-priority blockers
Resolve accidental noindex directives, conflicting canonicals, invalid metadata, insecure resources, missing mobile viewport settings, and broken structured data before polishing low-impact details.
StrictSEO reference library · 85 explained checks
Every StrictSEO finding links here. Choose an area to learn what the signal means, when it matters, how to repair it, and what evidence confirms the fix.
Resolve accidental noindex directives, conflicting canonicals, invalid metadata, insecure resources, missing mobile viewport settings, and broken structured data before polishing low-impact details.
StrictSEO explains what the rendered page shows. Response headers, robots.txt, status codes, field performance, rankings, backlinks, and search-engine selection still need their own evidence. Use the SEO and AEO audit guide to check those layers separately.
17 focused references cover every page check and every cross-page pattern in the current beta.
Fix missing, duplicated, or unclear page titles and meta descriptions across indexable pages.
Open explanation →4 checksConfirm which URL should be indexed and remove conflicting directives.
Open explanation →6 checksMake the page’s main topic, heading hierarchy, and semantic landmarks easy to understand.
Open explanation →7 checksStrengthen alignment, useful depth, readability, and decision support.
Open explanation →3 checksHelp readers identify who is responsible, when content was reviewed, and which evidence supports important claims.
Open explanation →2 checksMake important answers direct, self-contained, properly qualified, and easy for people or answer systems to extract.
Open explanation →4 checksMake informative images understandable, accessible, layout-stable, and appropriately sized for their rendered use.
Open explanation →6 checksCreate useful crawl and navigation paths with descriptive, intentional links that set clear destination expectations.
Open explanation →6 checksKeep structured data valid, visible, truthful, and relevant to the page content people can actually access.
Open explanation →4 checksConnect equivalent language and regional pages with complete, reciprocal annotations and clear default handling.
Open explanation →4 checksAlign Open Graph and X/Twitter previews with the canonical page and describe the shared image accurately.
Open explanation →4 checksGive browsers, crawlers, and assistive technology a predictable document language, encoding, and HTML foundation.
Open explanation →5 checksMake the rendered page readable and operable without zooming, tiny targets, or unintended sideways scrolling.
Open explanation →3 checksKeep public pages, active resources, and form destinations on secure, consistent HTTPS connections.
Open explanation →10 checksUse local performance evidence to identify the delivery, rendering, or resource cost that needs deeper measurement.
Open explanation →8 checksConnect rendered-page advice to the responses and discovery paths a crawler actually encounters.
Open explanation →5 checksUse the pages you visit to find repetition, collisions, and discovery gaps.
Open explanation →