A real estate website that has been live for twelve months is a different thing than the one that launched. Google has indexed most of it, visitors have found some of it, and real data exists about which pages work and which do not.
Most agents skip the annual audit that would turn that data into decisions. The reasons are consistent: nobody told them to do it, the tools feel technical, and a new website feels like a project that is supposed to be done once. By year two, the gap between what the site could be doing and what it is actually doing has widened enough that recovery becomes the work, instead of tuning.
The audit at one year is not a redesign. It is a few hours of looking at specific reports and making specific decisions about specific pages. Most agents come out of it with three to five clear next moves.
What is different at the one-year mark
Three things change between launch and twelve months that make this audit possible.
Search Console has a full year of data. The Performance report now shows which pages rank for which queries, average positions, impressions, clicks, and click-through rate. At month three, the data was too sparse to read. At month twelve, the patterns are clear enough to act on.
Analytics has a complete seasonal cycle. A real estate website runs through a predictable pattern: a slow January to late February, a surge from March through June, a quieter July and August, a second peak in September and October, and a wind-down in November and December. By month twelve, the analytics have seen one of each, which is enough to tell which traffic patterns are real and which were noise.
The site itself has accumulated enough weight to show problems. New listings, new blog posts, extra marketing pixels, additional images. Each one adds load time. Each one adds complexity. Core Web Vitals that passed at launch can quietly slip over twelve months, and the Core Web Vitals report in Search Console shows which pages are now failing.
The audit itself, step by step
The whole exercise takes a few hours of focused work. The output is a short document with per-page decisions and a list of next actions.
Step one: Search Console Performance, twelve-month view. Set the date range to Last 12 months. Switch to the Pages tab. Sort by Impressions, descending. The top twenty or so pages are the ones that earned attention. Look at three things for each:
- Average position. Pages at position 5 to 20 are candidates to refresh, because a focused content update can often move them into the top five. Pages at position 1 to 4 are already working, and the right move is usually to leave them alone or lightly update.
- Click-through rate. Compare the page's CTR to the general pattern for the position it is at (roughly 25 to 40 percent for position 1, 10 to 15 percent for positions 2 to 3, 5 to 8 percent for positions 4 to 5, and lower from there). A page ranking position 3 with a 2 percent CTR almost always has a title and meta description problem, not a content problem.
- Query mix. Click into the page and check the queries it ranks for. A page ranking for queries that do not match its actual content is a cue to either rewrite the page toward the dominant query, or recognize that the ranking is incidental and will not convert.
Step two: Search Console Performance, queries view. Switch to the Queries tab, same twelve-month range, sort by Impressions. The top queries show what Google thinks your site is about. A mismatch between the top queries and the business the agent actually wants to grow is the single most informative pattern in the report. If the top queries are for a neighbourhood the agent no longer specializes in, or for a service the agent dropped, the site is working on the wrong business.
Step three: Analytics, Pages and screens report. Open the Pages and screens report in GA4. Sort by Views and look at the top twenty pages. Cross-reference with conversion events (form submissions, phone clicks, lead captures). The pattern that matters is pages with high views and no conversions, which usually means traffic that is not matched to intent, and pages with moderate views and several conversions, which usually point at the pages the site is actually earning business from.
Step four: Core Web Vitals. Open the Core Web Vitals report in Search Console. Compare the pass rate to the launch state. Any page that slipped from pass to needs improvement or poor is on the list for a performance review, usually around images and third-party scripts.
Step five: Manual review of the top ten pages. Open each of the top ten pages by traffic in the browser. Read it. Check that every statistic is still current, every link still works, every mention of a product, process, or market fact still matches what you would say to a client today. Check that the agent bio, About page, and contact details are all accurate. Flag anything that is not.
The four decisions
Every page the audit touches gets one of four labels.
Keep as-is. The page ranks, converts, and contains no outdated information. Do nothing. Revisit next year.
Refresh. The page ranks or earns impressions but the content has specific updates that would improve it: new statistics, new sections, better internal links, updated imagery, an improved title and meta description. Schedule the refresh in the next two to three weeks.
Consolidate. Two or more pages cover the same topic and would be stronger as one longer page. Combine the content on the strongest URL, 301 redirect the others to it. This also addresses accidental keyword cannibalization, where multiple pages compete for the same query.
Retire. The page gets fewer than ten impressions per month across twelve months, the topic is no longer relevant to the business, and consolidating does not make sense. 301 redirect to the closest related current page. Google's helpful content system documentation describes maintained, up-to-date content as a quality signal, and retiring pages that drag on that signal is part of the ongoing work.
What tends to come out of the first annual audit
The audit usually surfaces a short, concrete list. Specifics differ by site, but common patterns:
Three to five pages ranking on position 5 to 20 with high impressions and low CTR. These are the highest-leverage refreshes. A rewritten title and meta description matched to the actual queries, plus a 30 percent content expansion, often moves a page from position 8 to position 4 within a few weeks.
A blog archive that is mostly unused. Most agent blogs have two or three top posts and a long tail of posts that earn nothing. Consolidating the tail and promoting the top posts to proper reference pages in main navigation improves both discoverability and overall site quality signals.
An About page or agent bio where one or two details are out of date. Usually a fixed-in-ten-minutes job that catches a specific trust issue before it becomes a conversion issue.
One or two pages with slipped Core Web Vitals. Usually caused by an added hero image, a new tracking script, or a chat widget. The fix is targeted rather than site-wide.
A mismatch between what the site ranks for and what the agent actually sells. The most important pattern to notice, even though acting on it is the longest-term work. The audit surfaces the gap; closing the gap is the content and structural work of the next six months.
When the audit suggests a rebuild and when it does not
An audit that produces a focused list of page-level actions is working as intended. The right response is to execute the list over the next two or three weeks and revisit in twelve months.
An audit that keeps surfacing the same kinds of structural issues (wrong URL structure for the content, no schema markup anywhere, a CMS that makes content updates slow enough that the agent avoids making them, no mobile responsiveness) is a signal that the site has outgrown its architecture. That is the case where a rebuild becomes the proportional answer, and where the free rebuild preview lets the agent see what the structural fix would look like before committing to it.
Most sites at one year are not in that second category. They have grown unevenly, picked up some performance debt, and have a handful of pages that would benefit from a refresh. That is the normal state, and the annual audit is how it gets maintained.
The takeaway
A real estate website at one year old has enough indexed pages, traffic data, and seasonal history to support an informed audit. The audit itself is a few hours of work across Search Console, GA4, and a manual review of the top pages. The output is a short list of page-level decisions (keep, refresh, consolidate, retire) and a sense of whether the site is still structurally sound or starting to show the strain of its original build.
Done once a year, the compounding effect is significant. Done once and never again, most of the value evaporates within another twelve months.
The website checklist post is a useful companion to the structural review, and the analytics what-to-track post covers the GA4 setup that makes the annual audit easier. The FAQ and contact page are good places to start if you want help running the audit against your own site.
