Website audit
Use the page scan and available technical checks to understand what needs attention. See the problem, the affected pages and the practical next step.
FROM FINDING TO FIX
A useful audit connects the issue to the affected pages and a practical next step. Explore these example findings.
Two example service pages share the same title, making garden design harder to distinguish from landscaping.
Next step Give each page a clear title based on its actual service and location. Review the wording before publishing.
Three entries in the sample sitemap lead to another address. The sitemap can point directly to the final pages.
Next step Use the final canonical URLs and check the updated sitemap. This finding does not predict a ranking gain.
Four project images in the fictional review need useful descriptions. An image’s purpose determines what alternative text it needs.
Next step Add concise, factual descriptions where they help people understand the page. Decorative images may correctly use empty alternative text.
The findings and counts are fictional. Opening this preview does not crawl a website.
Explore the site-health exampleA useful technical review identifies where an issue occurs and explains why it matters. Start with the affected pages and the information actually returned by the scan. Different websites and access conditions can produce different coverage, so check what was inspected before treating a result as an assessment of every page or system your business uses.
The app brings page-scan findings and AI-readability observations into the website context. Use them alongside your goals and important pages. A technical issue on the page that explains your main service may deserve a different priority from an issue on an old supporting page. The relevant next step is a defined fix, with someone responsible for carrying it through.
Read the suggested instructions, discuss the finding with Phii or check whether a suitable service is available. Confirm what will change and the access needed before implementation. After delivery, inspect the website and use an appropriate follow-up check. A completed audit means the findings are available; it does not mean the problems were automatically fixed.
Choose the site you want to inspect and review the scope of the check. A client’s second website needs its own context.
Look at the problem, affected pages and explanation. Separate confirmed observations from information that still needs checking.
Decide whether to make the change yourself, ask your agency or order an available service with a clear scope.
Check the implemented page and the relevant technical result. Use later evidence to see whether another action is needed.
No. Technical page checks inspect aspects of the website. AI visibility looks at answers to the questions included in an audit. Both can help inform a wider plan.
A Roast focuses on how a visitor experiences a page and what may stop an enquiry. Technical findings and a Roast often reveal different parts of the same journey.
No. A score summarises a particular check. Visibility and enquiries depend on other factors, including relevance, content, the offer and the wider market.
Check the available service and its scope in your account, or discuss it with your agency. Access, platform limits and the exact change need to be confirmed first.
Start with a free AI visibility check. Then choose the work you need.