01
Catch template-wide failures
See when the same metadata, canonical, structured-data, status-code, redirect, crawler-access, or internal-link defect appears across multiple pages.
Full-site Technical Audits
Stop fixing your site one page at a time
Foglift checks up to 100 pages in one full-site Technical Audit, shows which defects repeat, and ranks the weakest URLs so your team can fix the shared cause first.
Fix the cause once
Catch problems before they spread across the site
Turn a list of isolated page warnings into one repair plan. The site rollup exposes the pattern, and the page inventory shows every URL affected by it.
02
Find the pages dragging you down
Sort the page inventory by AI Readiness and move directly from the site average to the URLs that need attention first.
03
Prove the fix worked
Keep every completed report in Technical History, then compare the next run against the dated page evidence your team started with.
See the product at work
See the whole site in one report
Start with the site-wide answer, then move into the exact pages and evidence behind it. Every report keeps the crawl scope, score distribution, repeated defects, and page inventory together.
Inside every report
See the evidence behind the ranking
| 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? | 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
Turn one crawl into a repair plan
Move from the site-wide pattern to a focused repair, then use the next report to verify the result.
Scan the full domain
Start a full-site run when the seven-day availability opens. The audit discovers eligible URLs and selects up to 100 pages.
Spot the repeated pattern
Read the score distribution and Site Technical Analysis to find defects shared by a template, directory, or page type.
Prioritize the weakest pages
Sort the inventory by AI Readiness and open the supporting single-page report when you need element-level evidence.
Fix the shared cause
Group work such as schema, robots.txt, answer structure, canonical rules, and internal linking before isolated cleanup.
Verify the improvement
Use the next full-site report to confirm that the distribution changed and repaired pages moved out of the weak group.
A shared starting point
Give every team the same clear next step
Replace scattered audit notes with one dated report that connects the site-wide problem to the pages your team owns.
Standardize client reviews
Give every client the same technical review, a dated report, and the exact URLs behind each recommendation.
Clean up sprawling libraries
Find template-level defects and weak directories before another release repeats them across more content.
Verify launches and migrations
Capture canonicals, redirects, status codes, internal links, sitemap coverage, and crawler policy after launch, then confirm the next run.
Questions
Choose the right audit scope
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.
Fix the shared cause before another page ships
Start with a free single-page Technical Audit, then use Foglift full-site coverage to find every page carrying the same problem.