What it is.
The template calls DataForSEO to crawl up to 1,000 pages, pulls Search Console metrics for the same URLs, and merges them before scoring. Output is an HTML report you can brand and send.
Findings group into five buckets: status problems like broken pages and redirects, content quality including thin pages and readability, metadata, internal linking with orphan pages and click depth, and pages underperforming against their impressions.
The merge with Search Console is what separates it from a plain crawl, because a thin page with no impressions and a thin page ranking on page two are different jobs.
What you get.
- A crawl of up to 1,000 pages with metadata, content, and link checks.
- Search Console clicks, impressions, position, and click-through rate joined to each crawled URL.
- Five issue categories, including orphan pages and excessive click depth.
- A branded HTML report at the end, ready to send.
How to set it up.
Add a DataForSEO API credential, because the crawl steps will not run without one.
Connect Google Search Console with the property you want joined to the crawl.
Set the target domain and keep the crawl ceiling at the 1,000 pages the template expects.
Adjust the thin-content word threshold in the scoring node to match how your pages are written.
Edit the HTML template node with your own logo and colors if the report is going to a client.
Run it against a small site first, since a full 1,000-page crawl consumes DataForSEO credits.
Use cases
Crawl joined to performance
Pair the crawl with Search Console so each issue carries its traffic cost.
Prioritize by clicks at risk
Sort the findings by the impressions sitting behind them.
Repeat the audit monthly
Schedule the run and compare this month's report against the last.
Best for
A quarterly technical review
One run produces the document a review meeting needs, with the ranking data already attached.
Client-facing reporting
The HTML output is brandable, so the deliverable stops looking like a tool export.
Prioritizing a content cleanup
Thin pages with impressions get rewritten first, and thin pages with none get merged or removed.