See what holds your site back.
Turn a site review into a clear next step. Find technical issues, inspect the pages behind them and focus your next improvement. Add measured Google performance or optional market data when you need a wider view.
Illustrative crawl reportFictional site
See the pages. Find the next fix.
Missing title tag/collection
A sample of page findings, not Google rankings or traffic.
Illustrative data only. No site is crawled in this preview.
FROM FINDING TO NEXT STEP
Turn crawl findings into a clear next step.
Move from a broad site-health question to a specific page and a useful explanation. Review the severity, see the affected URLs and decide what to change in your site.
- Technical checks with the pages involved
- Titles, descriptions, links, headings and more
- Guidance you can take back to your site editor
Crawl findings describe the pages that were reached. They are not a guarantee of full-site coverage or search rankings.
Missing page title
The collected HTML has no page title. A clear, specific title helps describe what this page is about.
/collectionTitle: not found in collected HTMLAdd a descriptive title in your site editor, then collect another crawl to check the page again.
3 example issue types shown. Select a finding to inspect its evidence.
OPEN THE PAGE BEHIND THE NUMBER
Keep the evidence close to the page.
A report becomes more useful when you can inspect the URL behind it. Explore saved responses, metadata and page measurements without losing the context of the finding.
Saved page data.
A focused place to investigate.
/aboutHTTP 2004 example URLs shown. Fictional data; this page does not crawl a site.
Separate a missing title or description from a response with no HTML measurements.
Move from an audit finding to the affected page, then review the related page signals.
A saved crawl is a bounded sample at a point in time. An unreached URL is not proof of a deleted page.
ADD WHAT GOOGLE ACTUALLY REPORTED
Connect site findings with search performance.
Link an accessible Google Search Console property to review measured clicks, impressions, click-through rate and average position. Keep search performance distinct from what a crawl can tell you.
- 01
Connect with read-only access
Authorize Google and choose a property your account can access.
- 02
Map the property to your project
Choose the source explicitly, so the numbers stay connected to the right site.
- 03
Sync and explore the available window
Review measured queries and pages, with the period and data freshness in view.
Search Console is optional and requires a configured connection. Google’s reporting has a delay; this is not a real-time traffic counter.
Invented property and figures. This demo does not connect Google or represent customer results.
ADD MARKET CONTEXT WHEN YOU NEED IT
Your pages tell one story. Search data adds another.
A crawl can read your site. It cannot measure search demand or discover every site linking to you. Optional provider-backed research adds those perspectives when it is configured and available.
Explore the search demand behind a phrase.
Use provider-backed keyword ideas and available volume, difficulty and CPC data to add market context to your content research.
- DataForSEO-backed capabilities where enabled
- Provider access and usage budget required
- Unavailable results stay unavailable
FICTIONAL DATA · NOT A LIVE PROVIDER REQUEST
Illustrative provider estimates for a selected market. These are not clicks measured on your site.
ASK BETTER QUESTIONS AS HISTORY BUILDS
Give the next review some perspective.
Retained reports help you investigate changes and patterns over time. They answer from the history that exists, and show when there is not enough evidence to draw a conclusion.
Availability depends on the report’s source and collected history. Search Console measurements, provider data and modelled estimates are different kinds of evidence.
You choose the change.
Review the finding, update your site and return to the relevant reports. SEO does not apply automatic site fixes.
Which pages deserve a fresh look?
Review declines across retained page or search-performance history. Measured Search Console reports and modelled traffic estimates keep their source labels.
Enough comparable page history is required before the report can judge a decline.
This switch illustrates report states. It does not collect observations or change your project settings.
A CLEARER NEXT MOVE FOR YOUR SITE
Less guessing.
A better next step.
Start with the evidence you have. Build a review routine around the improvements that matter to your site.
Explore your site's healthFind a useful place to begin.
Turn a broad question about your website into a specific improvement you can understand and act on.
- 01Review the available crawl findings.
- 02Open the affected page and inspect its signals.
- 03Make a focused change, then review again.
MORE THAN ONE TOOL
Good work connects.
Your files, ideas, conversations and customers. Find their next home in AppStruct.
What do I need to run my first site review?
Choose a workspace and add a public domain. Where new site checks are enabled, review the available page and report allowance before starting a limited crawl. Saved audit results can be reopened without another scan. Core crawl findings do not require a Google connection or external search-data provider; availability and limits depend on your workspace and service setup.
Which problems can I investigate?
Review failed responses, broken URLs, missing or duplicate titles, missing descriptions, heading counts, canonical declarations and images without alt text. Audit findings identify affected URLs and explain what to review. Counts and checks describe the fetched sample, so a clean result does not establish that every page on the website was inspected.
Where do Google traffic and search positions come from?
A crawl reads pages; it does not measure Google search performance. When Search Console is available, connect Google, choose a property you can access and sync its reported clicks, impressions, CTR and average position. The property, date window and data freshness stay visible. Optional market-data tools use a separate configured provider and access allowance.
Can I inspect the evidence for an individual page?
Yes. Open a captured URL from the page inventory or an audit finding to review the available saved measurements, including its response, metadata, H1 count, word count and link counts. Fetch time describes the crawler’s request; it is not real visitor performance. Missing or unrecorded measurements stay separate from measured zero values.
Do I need optional market data?
Core audits work from fetched page evidence. Optional search-data tools add a separate provider’s keyword demand, search positions, backlink index and SERP comparisons when that provider is configured and access is available. These results have their own coverage and limits. Estimated traffic and modelled scores should be read as estimates, separately from measured Search Console data.
When can historical reports show useful results?
Reports such as content decay, query cannibalisation and share of voice need retained snapshots rather than a single page crawl. Their readiness states show when history, search volumes or competitor observations are insufficient. Where a report uses a model, it stays labelled; measured Google overlays are separate, and share of voice remains a modelled comparison.
Can I return to saved results later?
Yes. Saved crawler reports can be read again in the workspace that owns them, with their capture date and measured URLs. Opening a saved report does not start another crawl. Use its date and sample coverage when planning a new review; a saved observation describes the site when it was collected, rather than a continuous live monitor.
Will SEO automatically fix my site or guarantee rankings?
AppStruct helps you investigate and prioritize work; you decide which website changes to make. Rule-based findings and site-health scores organize the review rather than predict Google rankings. Check the affected pages, make the relevant updates and return to available evidence to evaluate the result. No audit guarantees search traffic, indexing or AI citations.
Do I need a separate account for each service?
No. Your AppStruct account gives you one place to access the services in your dashboard. See the pricing page for current plans and limits. View pricing →
APPSTRUCT SEO