Blog / Digital growth /
A midyear SEO review: what to look at in June
June is when the year starts to feel half-gone, and someone asks for “the midyear SEO report.” Cue screenshots of rankings and a verdict: good half or bad half. I’d rather use the moment to ask whether the work still fits the business.
In June, look at technical health, important pages, search data, the content plan and business outcomes. Then pick a small number of priorities for the next six months.
Use comparable data and be honest about its limits. Search demand and seasonality change, and the June 2024 spam update is still rolling out on 27 June. Separate what is known from what is uncertain, and do not attribute every movement to a single update or project.
Start with the business goal
Write down what the site is expected to support: enquiries, product discovery, online sales, readership or another outcome. Confirm whether the goal changed since January. A report that measures the wrong outcome can look positive while the business has a different problem.
Review GA4 key events and their definitions. Check that forms, calls or purchases are tracked correctly, and note any changes to analytics configuration. Search Console provides search visibility data such as clicks and impressions; analytics provides on-site behaviour. They measure different things and should not be merged casually.
Compare the first half with a relevant prior period, but account for seasonal patterns, campaigns, site changes and tracking issues. A year-on-year comparison may be more useful for a seasonal business than comparing adjacent months. Note when the data is incomplete or affected by a migration.
Check technical foundations
Confirm that important pages load, are indexable and return the right status codes. Check robots directives, canonical tags, redirects, sitemaps and internal links. Review Search Console for manual actions, security notices and indexing issues.
Test the site’s key journeys on mobile: product discovery, form submission, booking or checkout. Look at Core Web Vitals as LCP, INP and CLS. Use field reports where available and investigate specific pages when a metric looks weak. A technical audit should identify actionable issues, not generate a long list nobody owns.
Review backups, updates, access, hosting and monitoring. Website maintenance can prevent small issues from becoming outages. Check who owns domain and DNS access, whether recovery steps are documented and whether a recent backup can be restored.
Review content and search visibility
Identify pages that bring relevant visits, pages that have lost visibility and important topics with no useful destination. Look at queries and landing pages together. A page may receive impressions for a term that does not fit its purpose; that is a cue to review relevance, not to add the phrase repeatedly.
Check whether important pages are current, accurate and complete. Update details that have changed, merge overlapping articles when that improves the resource, and remove material only after considering links and user needs. Add original insight where it exists, but never invent client stories, results or expertise to make a page appear more authoritative.
Review internal links and navigation. Can people reach key services or collections? Do related articles support the next step? Are there old links pointing to deleted pages? Fix the routes that matter to visitors and crawlers.
Review the work plan
List completed tasks, blocked work and recommendations. Compare the list with the original plan. Did technical changes ship? Were content approvals delayed? Did the business add new products or markets? Explain dependencies and owners rather than presenting unfinished work as a result.
Choose priorities by impact, effort and evidence. Fix a serious indexing or conversion issue before polishing low-value metadata across hundreds of pages. Set a specific next step, owner and review date for each priority.
I wouldn’t turn every audit finding into a giant second-half plan. A short list actually gets done. Keep a backlog for lower-priority ideas and revisit it when capacity changes.
Treat updates with context
Google’s June 2024 spam update began on 20 June and is ongoing on the date of this post. Record the rollout and continue to monitor, but do not claim it caused a shift before it finishes and evidence is available. The March core update completed in April; do not combine separate updates into one explanation.
If traffic changes, compare pages, queries, technical status and demand. Search updates are one possible factor among many. Document the hypothesis and what evidence would support it. I won’t promise a recovery date or make broad changes just to look busy.
Make the next six months clearer
A good midyear review ends with decisions: what to keep doing, what to stop, what needs investigation and what work is next. Share the summary in plain language and let stakeholders ask questions. Record the baseline so the next review can compare like with like.
Turn the review into a short plan
A review is only useful if the next actions have an owner. After looking at the evidence, write a short list with the issue, why it matters, what change is proposed, who will do it and when you will check again. Separate urgent risks from worthwhile improvements. A broken checkout deserves a different queue position from a title rewrite that might improve relevance. If a task depends on a developer, a client approval or better product information, make that dependency visible instead of treating it as a task that can start today.
Choose a baseline that fits the work. For a technical fix, record the affected URLs and the current state. For content, note which pages and queries are being reviewed. For measurement, confirm that the event or report means what the team thinks it means. The June spam rollout is underway on the date of this post, so leave room to distinguish its possible effects from changes the team makes. A midyear review should reduce uncertainty, not pretend it can explain every fluctuation.
Related reading
- Client reporting in Looker Studio: a simple template
- The June 2024 spam update: notes for site owners
- How long does SEO take? An honest answer
Set aside time to review one business outcome, one technical risk and one content priority. What are the two or three actions that would make your second half more focused?