SEO / FIELD NOTES
DEVBD JOURNAL / PRACTICAL ADVICE
Your WordPress SEO audit: what to fix first.
Turn a long audit into a useful plan by checking access, important pages, and customer journeys in the right order.
A useful place to start · YOUR SITE, IN GOOD HANDS.
SEO / FIELD NOTES
READ IT. USE IT. GET ON WITH YOUR DAY.
ILLUSTRATIVE GUIDE
4 min
A practical read
SEO
The topic
Plain
English. Clear steps.
DEVBD / UPDATED 27 OCTOBER 2026 / SEO
An SEO audit should help you choose the next useful job. A long list of warnings is not a plan, and fixing every warning can waste a small business budget. I start with the pages that explain your main services or sell your products, then separate problems that block those pages from improvements that can wait.
Choose the pages that matter
Write down your main services, the places you actually serve, and the action you want a visitor to take. Pick a small starting set: your home page, key service or product pages, and contact page. Keep the wider site on your list, but give the pages connected to your business goals a clear owner and priority.
Save a baseline before changing anything
In Search Console, open the Search results Performance report. Note the date range and search type, then look at clicks, impressions, queries, and pages. Filter by country or device when relevant. Compare equivalent periods and remember that seasons, promotions, and changes in demand can affect the numbers. Google's Performance report documentation explains the available metrics and filters.
Check whether Google can reach the page
A blocked or broken service page deserves attention before a cosmetic title change. Open it yourself, then inspect its full URL in Search Console. Read the indexing reason, the last crawl information, and Google's chosen canonical URL. Use the live test to investigate the current page; the indexed report describes the version Google already knows. The URL Inspection guide explains that distinction and its limits.
Check unintended noindex settings, access restrictions, server errors, and wrong redirect destinations. Do not remove a restriction from private or staging content just to clear a warning. Google's technical requirements are a useful starting point for public pages intended for Search.
Make each important page useful
Read the page as a customer. Can you tell what is offered, who it is for, where it is available, and how to enquire? Give it a descriptive title, a clear heading, and relevant internal links. Answer practical questions using your own knowledge and real business details. Add genuine photos or evidence when you have them. Google's SEO Starter Guide explains these foundations without promising a first-place ranking.
Test the visit after the search
On a phone, open the page, use its menu, and try the contact form or checkout. Review Core Web Vitals alongside that journey. Loading, responsiveness, and layout stability matter, but a good score cannot fix an unclear offer or broken form. Use Google's Core Web Vitals guidance to understand the measurements.
Turn findings into a short work list
- Fix now: important pages unavailable, accidentally excluded, or sending visitors to a broken enquiry path.
- Improve next: unclear service information, missing useful internal links, or a repeatable mobile problem on a valuable page.
- Plan later: lower-value content additions and refinements that do not resolve a current blocker.
For each item, record the affected URL, evidence, proposed change, effort, owner, and check after completion. Keep a change log and reassess after Google has had time to process the work. A small, verified improvement is more useful than a clean-looking report with no business purpose.
Want a second pair of eyes? My SEO audit covers up to 50 pages for $490 and includes a ranked fix list. See the audit scope and ongoing SEO options.