01
Repeated defects become visible
Compare metadata, canonicals, structured data, status codes, redirects, crawler access, and internal links across the audited set.
Full-site Technical Audits
Find the defects repeated across your whole site
A single-page audit can confirm one URL is healthy. Foglift reviews up to 100 selected pages, exposes patterns that repeat across templates and sections, and ranks the pages that deserve attention first.
Why whole-domain evidence matters
One weak template can affect dozens of pages
AI engines retrieve pages, extract answers, and evaluate access one URL at a time. A missing canonical, blocked answer-search crawler, inconsistent heading structure, or absent JSON-LD often begins in a shared template. The same defect can then repeat across a product library, documentation set, or client site.
Foglift keeps the page-level evidence visible. The site rollup shows the pattern, while the page inventory shows exactly where it occurs. Teams can address the shared cause first and avoid repairing URLs in an arbitrary order.
02
Weak pages stay attached to the average
See the score distribution and page findings instead of relying on one site-wide number.
03
Every rerun becomes evidence
Technical History preserves the completed report, capture date, crawl scope, and page evidence for before-and-after review.
Measured evidence
What the report contains
The report keeps its answers connected to the URLs, counts, and technical observations that support them.
| Report section | What it answers | Evidence shown |
|---|---|---|
| AI Readiness across the site | Which pages need attention first? | Average, median, scored-page denominator, score distribution, sortable page findings |
| Sitemap evaluation | Did the crawl cover the URLs the site declares? | Sitemap type, declared URLs, documents captured, protocol limits, robots.txt reference |
| AI crawler access policy | Can answer-search crawlers reach intended public pages? | Purpose-separated crawler rules and the number of URLs checked |
| Internal architecture | Can crawlers and people reach important pages through the site? | Click depth, orphan pages, thinly linked pages, deep pages, strongest hubs |
| Consistency hygiene | Which technical defects repeat? | Origin status distribution, title and description defects, H1s, canonicals, redirects, JSON-LD, mixed content |
| Page inventory | Which URL should the team inspect next? | Page type, AI Readiness, citations, links in, freshness, fetch status, and saved single-page report links |
Crawler access is eligibility evidence. It does not prove that an engine indexed, cited, or recommended a page.Foglift keeps crawler policy, referral traffic, and answer-level AI Visibility as separate signals.
From crawl to confirmation
The five-step repair loop
Move from site-wide pattern to a focused repair, then use the next report to verify the outcome.
Run the full-domain audit.
Open Technical History and start a full-site run when the seven-day availability opens. Foglift discovers eligible URLs and selects up to 100 pages for the run.
Read the rollup.
Start with the score distribution and Site Technical Analysis. Look for defects that repeat across a template, directory, or page type.
Work down the weakest pages.
Sort the page inventory by AI Readiness and open the supporting single-page report when you need element-level evidence.
Turn findings into Actions.
Group shared fixes such as schema, robots.txt, answer structure, canonical rules, and internal linking. Assign the highest-impact work before isolated cleanup.
Rerun and compare.
Use the next available full-site audit to confirm whether the distribution changed and whether the repaired pages moved out of the weak group.
Dated production evidence
A bounded 100-page run
On August 13, 2026, Foglift's production activation canary discovered 787 eligible URLs on foglift.io, selected and analyzed the exact 100-page cap, and completed with zero page errors. The selector prioritizes commercially useful page types and citation evidence before applying the crawl budget. A large sitemap therefore does not become an arbitrary first-100 crawl.
The completed report recorded 100 analyzed pages and 687 URLs outside the crawl budget. The scope remains explicit so a reader can distinguish analyzed evidence from the wider discovered inventory.
Read the production updateWho uses full-site audits
Agencies
Standardize a technical review across client sites, preserve a dated report, and show the exact URLs behind each recommendation.
Large content libraries
Find template-level defects and weak directories before they spread across another release cycle.
Launches and migrations
Capture the post-release state of canonicals, redirects, status codes, internal links, sitemap coverage, and crawler policy, then verify the next run.
Questions
Full-site Technical Audit FAQ
What is the difference between a single-page and full-site Technical Audit?
A single-page Technical Audit measures one public URL across SEO, AI Readiness, performance, security, and accessibility. A full-site audit selects up to 100 pages, adds site-level sitemap, crawler-policy, internal-architecture, and consistency evidence, and preserves the completed whole-site report in Technical History.
How many pages does Foglift audit?
Each full-site run selects up to 100 pages. The report shows the discovered, analyzed, and outside-budget counts so the evidence boundary is explicit.
How often can I run a full-site audit?
Launch, Growth, and Enterprise include automatic weekly full-site coverage. An entitled workspace can also start a manual run when its seven-day availability opens.
Does a strong AI Readiness score guarantee citations?
No. The audit measures technical and structural readiness. Use AI Visibility monitoring to measure mentions, citations, sentiment, competitors, and share of voice across answer engines.
Are full-site audits free?
Unlimited single-page Technical Audits are available at $0. Full-site audits begin on Launch at $49 per month.
See the whole site, then fix the right page first
Review Foglift plans for weekly full-site coverage, or run a free single-page Technical Audit to inspect the page in front of you.