Workflow guide · 3 minute read
Crawl demo fixtures
Get familiar with SEO Crawler on a small test site with intentional issues. Run a scoped crawl, connect an issue to its matching rows, and practice a useful investigation before opening a client audit.
18-second workflow
Start with a known test site.
The test pages intentionally contain errors. Crawl time and issue counts can vary with the app version, fixture updates, and settings.
What happens in the demo
Start with the fixture URL
Use the public test pages in an empty crawl session.
Choose Subfolder
Limit the page crawl to the fixture path instead of the whole domain.
Run the crawl
After dismissing the address history, start the crawl and let the issue groups finish updating.
Inspect an intentional error
Select 4xx Client Errors and read its matching row beside the open Issues panel.
Select the affected URL
The broken-target fixture is an expected result, ready for a link investigation.
Keep the first crawl focused.
Use this fixture URL in the app:
- 1.
Start with an empty session
Export anything you need from an existing crawl before clearing it. The demo begins with an empty results table.
- 2.
Choose the fixture subfolder
Enter the full URL, open the scope selector beside the address, and choose Subfolder. Confirm that the command reads Crawl folder.
- 3.
Run the crawl once
Dismiss the address history if it is open, then click Crawl folder. Wait for completion before comparing issue totals. Keep the Issues panel open alongside Pages.
- 4.
Read an expected result
Select 4xx Client Errors. The broken-target URL is deliberately missing; its 404 is part of the exercise.
Expect issues by design.
Response codes
A deliberately broken destination and a chain of redirects give you known examples to investigate.
Find broken internal linksPage-level signals
Missing metadata, repeated titles, heading issues, and a canonical mismatch let you practice filtering and comparison.
Review canonical signalsResource access
Some pages reference CSS or JavaScript disallowed by robots.txt. Resource results depend on the crawl settings and features enabled.
Understand blocked resourcesDo not treat the demo totals as a health score or a fixed acceptance test. Read the URL and the underlying signal. A different count can reflect a newer fixture set, a different crawl scope, or a feature that is not enabled.
Repeat one investigation, then export.
Trace the broken destination back to its source, follow the redirect chain, or compare the canonical signals. When you can explain one finding with its affected URL, turn that small selection into a sample handoff.
Keep demo exports separate from client deliverables. Before your first real audit, check the target domain, scope, permissions, and crawl settings again.