Use a predictable scenario
Demo pages make it easier to see crawler behavior without waiting for a real site problem.
Website Audit Tool
Home / Metadata Issues Demo
Demo scenario pages
Metadata issues demo for title and description checks.
A curated scenario page for missing titles, duplicate metadata, noindex pages, and page-level metadata review.
✓Free during beta✓URL-level evidence✓Private history after signup✓Scheduled monitoring
What this check finds
This page focuses on metadata issues demo in crawl context. The crawler records the fetched URL, response status, discovery source when available, metadata, redirect outcome, and history signals that explain why a finding appears.
Use the check to review a curated demo scenario that shows how crawler evidence appears in the app. The goal is not just to report a problem, but to show the URL-level evidence needed to decide whether the issue is intentional, accidental, fixed, or still unresolved.
Metadata Issues DemoCompleted
Visited704
Indexable619
Errors20
Warnings8
FindingSeverityEvidence
Demo findingWarningPrepared URL-level evidence
Intentional error caseErrorSource page and status
Comparison signalsInfoChanged or persistent findings
Why this check matters
Inspect the same evidence model
The demo uses the same style of status, metadata, source-page, and history evidence as real crawls.
Move from demo to your site
After reviewing the scenario, run the same check against your own website.
How to use this demo
- Run a focused crawl. Start with the affected website or section and keep settings consistent for follow-up comparisons.
- Inspect the evidence. Review affected URLs, source pages, HTTP statuses, metadata values, and crawl lineage before making changes.
- Apply the smallest safe fix. Update the page, template, route, redirect rule, canonical tag, or internal link that caused the finding.
- Rerun the audit. Confirm that the finding is resolved and did not create a new issue elsewhere.
When to monitor it
Small technical issues become expensive when they remain invisible. For metadata issues demo, a repeatable crawl helps distinguish a one-time anomaly from a persistent problem caused by templates, redirects, routes, metadata, or content changes.
Start with the concrete evidence: affected URL, source page, HTTP status, metadata value, redirect target, or comparison row. After the fix is made, run another crawl with comparable settings to confirm the finding is resolved.
Frequently asked questions
What does this page check?
It checks a curated demo scenario that shows how crawler evidence appears in the app and presents the result as summary counts plus URL-level evidence. That makes the audit useful for deciding what to fix and for verifying the result in a later crawl.
Will the audit start immediately after I enter a URL?
No. The URL is transferred to the crawler seed field so you can review scope, limits, redirects, and sitemap policy before starting.
Can this be monitored over time?
Yes. Registered users can create scheduled audits and review whether findings are new, resolved, or still unresolved across completed crawls.
Is this only for SEO?
No. The same findings are useful for site maintenance, release validation, migration checks, and general quality assurance.
Related audit pages
Run the crawler on your own website.
Use the demo to understand the finding, then enter your own URL to inspect real crawl evidence.