Implement
flowseo_audits
Check your technical SEO before it costs you rankings
Site audit, Core Web Vitals, indexing and AI access in one place. You start audits yourself, and the other measurements run once a week.
Example data: Lumivo Werkhaus GmbH (fictional)
One audit in five views
-
Overview
Score, findings by severity, page status.
-
Problem report
Every finding with the affected pages, can be checked off.
-
Crawled pages
Every crawled page individually.
-
Crawl comparison
What has been added since the last audit and what is gone.
-
History
Every check across the last audits.
Core Web Vitals, separated by source
Field data comes from real Chrome users, lab data from a Lighthouse run. Google scores on field data, so FlowSEO labels both and names the measurement profile.
Example data: Lumivo Werkhaus GmbH (fictional)
| Metric | Good up to | Poor from |
|---|---|---|
| LCP | 2,500 ms | above 4,000 ms |
| INP | 200 ms | above 500 ms |
| CLS | 0.1 | above 0.25 |
Scoring uses the 75th percentile.
What else the weekly check looks at
The Technical page measures nothing at the push of a button. It shows what the weekly run found and can be read by everyone with access to the domain.
-
Indexing
Whether a page is indexed, why not, and which canonical Google chose. Requires a connected Search Console.
-
AI access
What robots.txt allows AI crawlers to do and whether your server lets them through.
-
Website checks
Address variants, redirects and sitemap.
Alerts about changes and problems
Monitoring reports changes and problems of a domain as alerts. One example: if clicks fall by at least 30 percent over seven days, from at least 100 clicks before, that is a critical alert and your domain team gets an email.
You read and acknowledge alerts in the browser and through your agent.
How your agent asks for it
Your agent reads audits, comparisons and the weekly check and marks findings as done.
- Starting an audit counts as a limited action.
- It cannot acknowledge alerts.