Documentation
Your ongoing workflow
Thirty minutes a week beats an eight-hour session once a quarter. SEO problems arrive continuously, so the routine matters more than the effort.
After your first scan
Resist fixing everything at once. In your first week:
- Read, do not fix. Understand the shape of the problem first
- Verify a handful of issues against your live pages, so you trust the data before acting on it
- Fix only the Critical band, indexation blockers first
- Record your starting score. It is a baseline, not a grade
- Connect Search Console if you have not already
Every week — about 30 minutes
1. Review new issues (10 minutes)
Filter to issues found since your last review, sorted by severity. A sudden spike in one issue type usually means a template or plugin changed, not that 200 pages independently broke — fix the template.
2. Approve safe fixes (10 minutes)
- Alt text, schema, Open Graph: bulk-approve with a spot check of two or three
- Titles and meta descriptions: read each one — they are what a searcher sees
- Canonicals, robots, sitemap, internal links, H1s, local business facts: read carefully, every time
3. Review Autopilot activity (5 minutes)
If enabled. Look for changes you did not expect, low-confidence applies, and anything on a commercially important page.
4. Check your change history (5 minutes)
Verdicts on changes whose measurement window has closed. Read the regressions specifically — they tell you which fix types work on your site, which is more useful than any average. If a fix type keeps regressing, stop auto-applying it.
Every month — about two hours
- Run a full crawl rather than an incremental one. Sites drift
- Compare scores against last month, with the issue delta that explains the change
- Review Search Console — queries, impressions, click-through, coverage errors
- Review rankings and competitor positions, where your plan includes a rank-data provider
- Review content — opportunities, decay flags, and cannibalisation
- Review the binding constraint on your priority keywords, including when it names something Crawlix cannot fix
- Pick three priorities for next month. Three, not thirty. Write them down
How to prioritise
Most sites have hundreds of low-impact warnings and three high-impact problems. Spend your time here:
| Impact | What it covers |
|---|---|
| High | Indexation blockers, broken redirects, missing or duplicate titles on commercial pages, Core Web Vitals on high-traffic templates, missing schema on product or article pages, thin content on pages meant to rank, orphan pages |
| Medium | Meta descriptions, heading structure, image alt text, internal link depth, Open Graph, sitemap completeness |
| Low | Cosmetic schema warnings, minor length deviations on titles that already read well, alt text on decorative images |
Measuring progress
Four things worth tracking, in rough order of usefulness:
- Change history verdicts — did each change actually help? This is the only measure tied directly to your own work
- Critical issue count — should trend toward zero and stay there
- Search Console impressions and clicks — Google's own view
- Your score — useful as a trend, meaningless as a grade
Worth knowing
Rankings move for reasons that have nothing to do with you: competitors change, algorithms update, intent shifts. Attribute carefully, and be suspicious of any tool that claims credit confidently.
Reporting and export
| Output | What it is |
|---|---|
| PDF report | A point-in-time scan summary |
| Change history export | Every change, prediction and verdict, as CSV |
| Shareable report link | A read-only public link that you can revoke. Open it in a private window before sending, so you see exactly what the recipient sees |
| Public API and SDKs | Bearer-key REST access, with JavaScript and Python clients |
| Webhooks | Event subscriptions for your own systems |
Not currently supported
Scheduled reports emailed on a recurring basis are not currently supported.
What good looks like after three months
Not a number. These:
- Critical issues stay near zero because you catch them weekly
- You know which fix types work on your site, from measured verdicts
- Your content plan comes from data rather than guesswork
- You know what is limiting your priority keywords, including the parts Crawlix cannot fix
- You spend time on the three things that matter instead of 300 warnings
If you are three months in and cannot say those things, tell us — that is a product problem, not a you problem. Start with troubleshooting.