Project overview and crawl health
Check crawl status, page availability, redirects, depth and issue groups from the project overview.

Keep crawl snapshots, URL Explorer, project issues, internal PageRank, link opportunities and Google Search Console analysis together for one site.

An SEO Project stores crawl snapshots and keeps findings attached to the affected URLs. That makes it possible to compare what changed instead of rebuilding an audit from separate exports.
Broken canonicals, redirect chains, blocked pages, slow responses and indexability conflicts.
Duplicate titles, missing headings, thin pages and metadata gaps.
Orphan pages, crawl depth, sitemap differences and low-inlink URLs.
Near-duplicate content groups and pages that may compete for the same search intent.
Existing link relationships, PageRank and relevant opportunities that are not linked yet.
Add the site, sitemap and crawl scope.
Start on demand or use the crawl schedule available for your plan.
Open technical, content, metadata, structure and GSC analysis views.
Drill into metadata, links, issues, keywords and crawl history per URL.
Start with project health, then open the URLs, issues, links and Search Console views that need attention.
Check crawl status, page availability, redirects, depth and issue groups from the project overview.

Inspect status, indexability, canonical, PageRank, inlinks, depth and sitemap presence per URL.
Open technical, content, metadata and structure findings with severity and URL-level explanations.

See how internal authority moves through the crawled link graph and which pages receive little support.
Incoming and outgoing relationships remain available at URL level.
Group near-duplicate pages for canonical, consolidation and cannibalization review.
Connect queries with landing pages and review cannibalization, CTR gaps, decay, movers and indexing views.
Compare periods per URL and open the queries that explain gains, stability or decline.
Compare snapshots, find repeated URL renames and review sitemap and structural differences.
Keep each client domain in a separate project with its own crawl configuration, GSC connection and history.
URL Explorer, issue reports and performance exports stay attached to the project instead of being rebuilt from separate crawl files.
Review broken product pages, metadata gaps, duplicate listings and internal link depth from the same crawl.
Parameter variants remain visible, so filtered or generated product URLs are not silently merged into a cleaner dataset.
Check new articles for accidental noindex, missing titles, orphan status and competing URLs.
Connect GSC to add query drivers, cannibalization, CTR gaps and content decay to the crawl-based checks.
Add the site, connect GSC when needed and keep crawl, issue and performance data in one project.