Google's September 2026 spam update finished rolling out on October 8. If your contractor website lost organic visibility around that time, you now have several weeks of data to help investigate what changed.
Start with the data before changing the website. A decline during an update does not, by itself, mean Google identified your site as spam. Seasonal demand, indexing problems, website changes, and shifts in the search results can also affect performance.
Your first step is to identify which pages and searches lost visibility, rule out other causes, and then review the affected content against Google's spam policies. That gives you a reason for each change you make.
What did the September 2026 spam update do?
According to Google's Search Status Dashboard, the update ran from September 24 through October 8 and applied globally, across all languages. It lasted 13 days and 16 hours, making it the longest of the four spam updates Google had listed for 2026 as of early November.
Google describes spam updates as improvements to the automated systems it uses to detect search spam. Sites that violate its policies may rank lower or disappear from search results.
That is different from a core update, which involves broader changes to Google's ranking systems. The distinction matters when you investigate a decline: losing rankings does not automatically establish a spam violation.
It also does not mean Google banned AI content. Its scaled content abuse policy addresses large amounts of content created primarily to manipulate rankings without helping users, regardless of whether people, AI, or a combination produced it.
For a contractor, the useful question is whether each page helps a prospective customer understand a service, evaluate the business, or decide what to do next.
How do I check whether my website lost visibility?
Start in Google Search Console. This initial review helps you narrow the problem; it cannot confirm an algorithmic spam action.
1. Compare performance before and after the rollout
Open Performance → Search results and compare September 10–23 with October 9–22. These equal, two-week windows give you a starting point outside the rollout itself.
Review clicks, impressions, click-through rate, and average position together. Fewer clicks with steady impressions and positions suggest a different issue from a broad loss of impressions and rankings.
Then widen the view. Check the longer trend and, where available, compare with the same period last year. An HVAC company's search demand can change substantially between September and October as temperatures and service needs shift.
2. Identify the affected pages and searches
Within the Performance report, select the Pages tab to see which URLs lost clicks and impressions. Use the Queries tab to examine the searches associated with those losses.
Separate branded searches from service searches. A decline in searches for your company name deserves a different investigation from a decline in searches for air conditioning repair.
Also look beneath the totals. Stable sitewide traffic can conceal losses on valuable service pages if other pages gained traffic during the same period.
3. Review when the decline began
Look at the daily trend before, during, and after September 24–October 8. A sustained decline that begins during the rollout makes the update one possible explanation.
Timing is a clue, not proof. Compare it with your own change history: a redesign, migration, URL change, tracking adjustment, or indexing directive may provide another explanation.
4. Check manual actions, security, and indexing
Open Search Console's Manual actions and Security issues reports. A manual action has a notification and a separate review process. An automated ranking change does not come with an individual spam penalty notice.
Next, review Page indexing and use URL inspection on important affected pages. Check for accidental noindex instructions, unexpected canonical URLs, inaccessible pages, or other changes that could prevent the right content from appearing in Search.
An empty Manual actions report does not rule out an algorithmic issue. It simply tells you that a manual action is not the explanation shown there.
Which contractor website content should I review?
Once you know what lost visibility, review those pages for specific problems. Google's spam policies cover more than the examples below, but these are useful places to start.
Scaled pages with little additional value
Publishing many pages is not automatically a violation. Neither is using a template or AI assistance.
The concern is producing large amounts of content primarily to capture rankings while adding little value for customers. If a service-and-city page changes only the location name, ask what it contributes beyond the other pages on the site.
Useful additions might include accurate service availability, relevant project examples, original photos, or answers to questions customers in that area actually ask. Add them where they help the reader, rather than treating them as a checklist that guarantees compliance.
Location pages that function as doorways
Separate location pages can help customers understand where you work and what you offer. They become a concern when substantially similar pages exist to capture similar searches and funnel visitors to another destination without being useful themselves.
Evaluate each page's purpose. Can a resident find meaningful information and take the next step directly from it? Does it accurately represent where and how your business operates?
The answer should guide your decision to retain, improve, or consolidate it.
Content hosted mainly to exploit your domain's reputation
Site reputation abuse involves third-party content published mainly to benefit from a host site's established ranking signals.
Hiring an agency or freelance writer does not, by itself, create this problem. Neither does publishing a useful contribution from a partner. The concern is an arrangement that uses your domain's reputation to rank content that would otherwise struggle to earn that visibility.
If you find an unfamiliar section promoting unrelated products or businesses, investigate who placed it there and why. Editorial supervision alone does not determine whether the arrangement complies with the policy.
Scraped content, link spam, and hacked pages
Look beyond the pages your team intentionally published. Check for copied articles with no added value, unnatural keyword repetition, manipulative link arrangements, and unfamiliar URLs introduced through a compromised website.
If an agency acquired an expired domain as part of your search strategy, review its purpose too. Buying an expired domain is not inherently abusive; repurposing one primarily to manipulate rankings with content that provides little value can be.
What should I fix first?
The order depends on what the investigation finds. A security compromise or indexing mistake needs a different response from repetitive content.
First, address access, security, and indexing problems. If important pages are blocked, unavailable, or compromised, resolve those issues before treating the decline as a content problem.
Next, group affected pages by type and assess their purpose. Export the declining URLs and organize them into service pages, location pages, blog posts, and other relevant groups. Similar losses can help you prioritize a review, but they do not establish the cause on their own.
Then make page-level decisions. Keep pages that serve a distinct customer need. Improve pages whose purpose is useful but whose information is incomplete. Consolidate substantially overlapping pages where one stronger resource would better serve the visitor. When consolidating, redirect retired URLs to the most relevant replacement and update internal links.
Avoid deleting every low-traffic page or reducing the number of location pages to meet an arbitrary target. Traffic alone does not tell you whether a page is useful, and Google does not prescribe a safe page count.
Address confirmed policy violations. Remove or otherwise resolve violating content using Google's guidance for the specific issue. Moving it into another folder or subdomain is not a reliable way to resolve the underlying problem. If there is a manual action, follow the instructions in that report.
Pause any workflow that is repeating the problem. If a content package or automated process is producing pages with little customer value, revise the process before publishing more. Review standards should apply whether the content comes from an employee, an agency, or an AI agent.
Finally, record which URLs changed, what you changed, and when. Continue monitoring the affected pages and queries alongside business outcomes such as qualified inquiries. A clear change log makes future performance easier to interpret.
How long can recovery take?
Google says changes may help if its automated systems learn over a period of months that a site complies with its spam policies. That is not a guaranteed recovery timeline or a promise that previous rankings will return.
There is no reconsideration request for an algorithmic ranking decline. That process applies to manual actions. Recovery also depends on the cause: fixing an accidental indexing block is different from resolving a longstanding content pattern.
After making changes, monitor the results over time. Avoid repeatedly rewriting or removing pages just because rankings have not immediately improved.
What should contractors do now?
Review your search performance, identify where visibility changed, and investigate the cause before committing to a cleanup or redesign.
For ongoing content, give every page a clear customer purpose. Keep service information accurate, make location pages useful, and review what automated publishing workflows produce. Those practices support a stronger website, even though no approach can guarantee protection from ranking changes.
If your organic visibility declined during the rollout, CI Web Group can review your Search Console data and website content to help determine what needs attention and which changes to prioritize.
