A public site audit catches mismatched settings before customers do. Review domains, navigation, SEO, redirects, analytics, senders, privacy, and publishing state before important launches.

What this guide helps you do

• Check public-site settings in one pass.
• Find stale links, missing tracking, and unsafe placeholder content.
• Create a launch or cleanup action list.

Before you start

• Know the primary domain and the pages that must be live.
• Have access to Website, Settings, Analytics, Domains, Mailboxes, and Navigation.
• Decide which items block launch and which can wait.

Do it manually

1. Check Domains for active domain and SSL status.
2. Review navigation, footer links, and important CTAs.
3. Open key pages and confirm title, SEO fields, forms, media, and links.
4. Check redirects for moved pages and alternate domains.
5. Confirm analytics, Search Console, sender mailboxes, and notifications are connected.
6. Create tasks for every issue and assign owners before publishing or announcing the site.

Ask Faster AI

• Create a public site settings audit checklist for this workspace.
• Review these launch notes and identify missing domain, SEO, tracking, sender, and navigation checks.
• Summarize what still blocks launch in plain language for the business owner.

Review before saving or publishing

• Do not expose preview URLs, private screenshots, internal notes, or customer data.
• Verify the live domain rather than only a branch preview.
• Check customer-facing forms and payment links with safe test data.

Common issues and fixes

• If a page is live but not in navigation, add it or document why it is hidden.
• If the domain is pending, fix DNS before launch communications.
• If analytics is missing, connect it before paid traffic starts.

Page SEO fields and structure

For how page-level SEO fields, headings, social previews, and redirects belong in every public-site audit, read the page SEO article. Page SEO Basics: Titles, Descriptions, and Structure That Rank.

Website speed that visitors feel

For why a public-site audit should include hero image weight, layout shift, third-party widgets, and mobile speed feel, read the website performance article. Why Your Website Feels Slow (and the Fixes That Matter).

Custom domain setup

For why domain, SSL, redirect, and email-record checks belong in every public-site launch audit, read the custom domain article. Connect a Custom Domain Without the DNS Headache.

Placeholder media

• Screenshot placeholder: add an annotated screenshot of audit your public site settings with customer names, email addresses, private domains, DNS values, amounts, internal notes, and unpublished content blurred.
• Video placeholder: add a short walkthrough that starts from the relevant Faster workspace area, shows the manual path, then shows how to ask Faster AI and review the result before saving, publishing, sending, or applying work.

Related help

• Connect a custom domain
• Connect site analytics
• Publish a page safely

Use it in daily operations

• Write down which workspace setting changed, who approved it, and which public page, sender, integration, role, or analytics view should be checked afterward.
• When a setting affects customers, emails, payments, domains, or public URLs, test the visible workflow before treating the configuration as done.
• Ask Faster AI to prepare the review checklist, but keep credentials, payment details, and sensitive customer data out of prompts and screenshots.