Find the explanation behind the next step.
Start with the question in front of you. Find the evidence a check needs, the reasoning behind a repair or a worked example from our own website.
Explore the library.
Broken internal links
Find every source page and discovery context behind broken internal links, group shared causes, and verify that removed references are really gone.
Explore the checkSEO checkRedirect chains
Audit redirect chains with source context, complete hops, final outcomes, and root-cause grouping instead of a flat list of redirecting URLs.
Explore the checkSEO checkCanonical targets that redirect
Find canonical declarations that do not resolve directly to a successful final page, with response paths and source-page evidence.
Explore the checkSEO checkMissing reciprocal hreflang
See both sides of every missing hreflang return link, the target's actual declarations, and the exact reason reciprocity failed.
Explore the checkSEO checkHreflang targets returning non-200
Find hreflang targets that redirect, fail, or resolve behind access controls, while preserving both sides of the language pair.
Explore the checkSEO checkMissing, empty, or hidden H1
Distinguish a truly missing H1 from empty markup, hidden variants, and localized template gaps with ordered heading evidence.
Explore the checkSEO checkMultiple visible H1 headings
Inspect every visible H1 in order with selector and component context instead of counting hidden responsive variants as duplicate headings.
Explore the checkSEO checkDuplicate page titles
Find repeated visible title text, preserve affected pages and language context, and separate true duplication from display-width guidance.
Explore the checkSEO checkMissing or derived meta descriptions
Separate truly missing meta descriptions from CMS excerpts, theme fallbacks, empty SEO fields, and derived visible copy.
Explore the checkSEO checkDuplicate meta descriptions
Group repeated meta descriptions across indexable pages and retain source, language, width, and CMS fallback evidence.
Explore the checkSEO checkUnparseable JSON-LD
Find syntactically invalid JSON-LD blocks before field-level schema checks, with exact page and discovery context.
Explore the checkSEO checkInvalid structured-data values
Find invalid dates, unresolved placeholders, and search-feature-specific schema values with exact node, field path, and root cause.
Explore the checkSEO checkImages missing intrinsic dimensions
Group missing width and height evidence by template, markup, content, or WordPress attachment while preserving every page and asset.
Explore the checkSEO checkHeavy referenced images
Trace heavy image assets and responsive variants to every live source page, then prioritize excess bytes across repeated delivery.
Explore the checkSEO checkSitemap and indexability conflicts
Find genuine indexable pages missing from sitemaps and sitemap URLs excluded by redirects, noindex, errors, or canonical decisions.
Explore the checkSEO checkTransient and confirmed 5xx responses
Distinguish temporary server failures from confirmed 5xx pages using bounded retries, backoff, cache evidence, and post-crawl verification.
Explore the checkGuideHow to verify an SEO fix without running another full crawl.
Use rule-scoped, source-aware evidence to verify a technical SEO repair while preserving the original crawl and knowing when a full crawl is still required.
Read the guideGuideHow to compare SEO crawls without manufacturing improvement.
Compare SEO crawls with compatible rule models, absolute counts, indexability movement, coverage states, and explicit release context.
Read the guideGuidePublic crawl evidence versus WordPress evidence.
Understand what a public crawler can prove, what a read-only WordPress snapshot can explain, and why the two evidence layers should remain separate.
Read the guideGuideHow to diagnose reciprocal hreflang failures.
Diagnose missing hreflang return links by keeping both pages, their actual declarations, response paths, canonicals, and language-cluster evidence together.
Read the guideGuideHow temporary 5xx responses distort technical SEO audits.
Reduce false server-error tasks with global request pacing, bounded retries, backoff, cache evidence, and separate recovered versus confirmed outcomes.
Read the guideGuideHow to turn repeated SEO findings into root-cause repairs.
Separate occurrences, affected entities, source pages, and root-cause groups so repeated crawl findings become focused repair tasks without losing evidence.
Read the guideComparisonA Screaming Frog alternative for connected team workflows.
Compare Screaming Frog's expert desktop crawler workflow with Amplitera's shared browser workspace, connected evidence, history, Re-check, and MCP access.
ExploreCase studyHow Amplitera verified its own 45-page SEO launch.
See how Amplitera found and repaired production navigation, metadata placement, duplication, contrast, and crawlability issues across its 45-page launch.
Read the case studyStart with your website.
Keep the evidence, the team and the next step in one working context.