In this article
How to do a website audit before choosing a rebuild?
To review a website before a rebuild, start with one customer action: a call, inquiry or booking. AI Growth Systems checks whether that action reaches its destination before recommending a rebuild. Keep the current URL, device width and received record beside each finding in the audit log.
Which URLs should the inventory include?
List public service pages, campaign pages and contact destinations in a sheet. Give each URL its purpose, owning service and intended action. Flag duplicate buying intent before adding pages. A plan to change an address also needs the destination for its redirect, the rule that sends an old URL to a new one. Save the review date.
| Field | Record |
|---|---|
| 1 | URL or task |
| 2 | Question or trigger |
| 3 | Approved source |
| 4 | Observed result |
| 5 | Owner and date |
How do you test the page on a phone?
Check a representative 390-pixel-wide screen as a test condition, then record the actual device and browser. Read the offer, open the menu and complete the form with the keyboard. Look for clipped labels, sideways scrolling and error text that a person cannot reach. Repeat the agreed path on desktop.
How do you verify that a form works?
Send a clearly labeled test through the approved contact path and confirm the saved record in its destination. Check required fields, validation errors and the visible confirmation. A 200 server response alone does not prove the receiving team has the inquiry. Remove test records under the owner's agreed procedure. Save the review date.
Which search and performance checks belong in the audit?
Inspect canonical URLs, indexing rules and internal links beside the page inventory. Use Google Search Console for indexing observations and PageSpeed Insights for a performance report. Record the date and tested URL. Keep measured loading results separate from a claim that one speed change will produce new inquiries.
| Case | Check |
|---|---|
| 1. Valid record | Saved and reviewed result |
| 2. Missing fact | Missing fact recorded without invention |
| 3. Conflict or failure | Named owner review |
How do you rank and verify corrections?
Give each finding an affected URL, customer action, proposed correction and acceptance test in 4 fields. A lost inquiry takes priority over a cosmetic change on the same path. After the fix, repeat the original test and save the received record. Keep redirects and successful paths in the launch checklist. Save the review date.
Sources and further reading
Read the original guidance alongside the practical examples in this article.