FlashCrafterArticle
October 2026: Google’s August spam rollout lasted 2 days, 16 hours. What changed, what the data measures, and how to check local losses.
Owners of independent local service businesses in the United States.
Google confirmed an August 2026 spam update. It began August 18 and finished August 21. Google did not list an August core update. That distinction matters if you are trying to understand a drop in your plumbing, electrical, cleaning or other local service business’s visibility: the announcement establishes a rollout, but it does not explain your individual results.
Some accounts saying that nothing was confirmed in August were written before the announcement. Others discuss early-August volatility while using language that sounds like a conclusion about the whole month. Read those dates carefully before using an article to explain lost calls or a change in rankings.
Checked October 17, 2026, the picture is clearer than the early headlines suggested. A large organic-search study recorded substantial ranking losses in its sample. It did not measure Maps losses, completed calls or booked jobs. Your next decision should connect the timing of your decline with website performance, Business Profile interactions and actual business records before you commit to a recovery service or remove useful pages.
The argument
The August 2026 event was a confirmed global spam update, but a rollout date alone cannot diagnose a local business’s decline. Separate organic rankings, Maps visibility, profile interactions and booked work, then use Google’s policies and your own records to decide what needs fixing and what deserves further investigation.
Google named the event the August 2026 spam update and said it applied globally across all languages. Its incident record gives a start of August 18 at 09:27 PDT and completion on August 21 at 01:49 PDT. The ranking-history page rounds that duration to 2 days, 16 hours.
There is no August core update in that history. The preceding listed core update began May 21, 2026. Calling the August event a core update changes the event’s identity and can lead you toward advice written for a different kind of rollout. When checking an agency explanation or an article, start with the name and dates in Google’s own record.
Early August needs a separate treatment. Google’s history contains no confirmed ranking update for August 1–6 or August 12–13. That does not establish that rankings were static during those windows. It means the record does not confirm a named rollout for those dates. A business noticing a change then still needs to investigate the change without automatically attaching it to the later spam update.
The subsequent September 2026 spam update also matters when reviewing a longer decline. It began September 24 at 09:15 PDT and ended October 8 at 01:00 PDT. Google lists its duration as 13 days, 16 hours. An account that still describes that rollout as ongoing is out of date as of October 17.
Google’s August notice does not publish an affected-query percentage, an industry breakdown, a local-business loss rate or a Maps impact figure. It also does not identify a particular list of spam tactics targeted in that rollout. The notice links to general spam-update guidance. Those limits leave room for investigation, but they do not support a claim that a particular trade, city-page format or Business Profile problem explains every loss.
| Item | Confirmed detail | What it establishes |
|---|---|---|
August event | August 2026 spam update; global, all languages | A confirmed spam rollout, not a listed August core update |
Start | August 18, 2026, 09:27 PDT | The official beginning of the rollout |
Completion |
Google Search Status Dashboard incident records and ranking history, accessed October 17, 2026. All times shown are PDT.
The strongest numerical account here concerns organic web results. SE Ranking’s own published post reports that 16.71% of previously top-10 URLs fell beyond position 100 during the August comparison, against 9.2% in the baseline. Search Engine Land’s August 27 report describes that as an 82% increase, or approximately 1.8 times the baseline. Those descriptions concern the change between the measured rates.
The sample covered 100,000 US keywords across 20 industries. It compared August 17 with August 22, using July 26 versus July 31 as the baseline. This gives you a concrete before-and-after window around the confirmed rollout. It does not establish a loss rate for independent service businesses or show that the same change occurred for the searches that bring your business customers.
The measurement stopped at position 100. A URL disappearing from that tracked range could have fallen below 100; the study cannot distinguish that outcome from deindexing. Describing every disappearance as removal from Google would make the finding stronger than the measurement allows. The analysis also did not identify losing page types or spam tactics at URL or domain level.
There was upward movement as well. Entries into the top three from outside the top 20 reached 12.86%, compared with an 11.5% baseline. Search Engine Land describes the change as a 12% increase. That is a relative increase, not a 12-percentage-point increase. Top-three entry means reaching positions 1–3; it does not mean taking first place.
For an owner, the practical lesson is to keep the unit of measurement attached to every number. These are URL-position changes across a keyword sample. They are not percentages of businesses penalized, customers lost or revenue reduced. They also provide no local-pack estimate. The figures support taking an organic decline seriously while leaving its cause and commercial effect to be established from your own records.
A decline in website visibility and a decline in business are related questions, but they require different evidence. Search Console helps identify changes in website queries and pages. Business Profile performance reports interactions with the profile. Your call and booking records show what happened after those interactions. Keeping these records separate prevents one weak signal from becoming an explanation for the whole business.
Google defines Business Profile “Calls” as call-button clicks. That metric does not establish that a call connected, that someone answered or that a customer booked work. “Website clicks” counts clicks on the website link in the profile. It does not establish what the visitor did afterward. A report should preserve those definitions when presenting a decline or an improvement.
Likewise, the organic keyword study cannot answer how much Maps visibility changed. No published August 2026 US local-pack impact study is identified here, and no measured percentage of local service businesses affected or average loss in calls, bookings or revenue is available. You cannot turn the 16.71% URL figure into a local-business loss forecast.
The useful question is where the evidence begins to change. A Search Console decline may be concentrated in particular services or pages. Profile interactions may follow a different pattern. Actual bookings may change by a different amount again. Compare those records without assuming they must move together or share a cause.
For any explanation you receive, ask which measurement supports it. A statement about organic rankings should point to website search data. A statement about profile activity should name the relevant interaction. A statement about lost jobs should connect to business records. Google’s rollout announcement supplies the calendar context; it does not supply those links for your business.
Start with the date the decline began. Write down when website search performance changed, when profile interactions changed and when your business noticed a change in calls or bookings. Compare those dates with August 18–21 and, if the decline continued later, September 24–October 8. A date match helps organize the investigation; it does not prove that either rollout caused the change.
Next, open the longer Search Console view. Google recommends using 16 months of data to identify seasonality, then comparing periods and examining queries, URLs, countries, devices and search appearances. A narrow view around one announcement can leave you without the context needed to judge whether the pattern is unusual for your business.
Then identify which pages and queries account for the decline. Keep that detail in the record rather than reducing the issue to a single sitewide percentage. The relevant work depends on what changed: a particular page, a group of service queries or a broader pattern. Google’s diagnostic guidance supports investigating those dimensions before deciding what needs repair.
Review Business Profile performance separately. Record call-button clicks and website-link clicks using their actual names. Compare them with your completed-call and booking records. This gives you a basis for discussing business impact without presenting a profile interaction as a customer outcome.
After that, inspect the pages and practices that could raise a policy concern. Google’s spam guidance supports reviewing compliance, including doorway pages and scaled-content abuse. Make the review specific to how a page helps a visitor and how it was created. The existence of a city name or the use of a particular production method does not by itself complete that assessment.
Finally, document the changes you make and the evidence you expect to review afterward. Google says improvements following spam-policy compliance may take months as automated systems learn that a site complies. There is no fixed recovery deadline. A provider should be able to explain the work and the measurements without promising a return date that Google has not published.
Keep the core-update timing rule in its proper context. Google’s core-update page advises waiting at least one full week after completion, then comparing with a week before rollout. August’s confirmed event was a spam update. That particular instruction should not be presented as an August spam-recovery rule.
City and service-area pages deserve an individual review. Google’s doorway examples include substantially similar pages and region or city pages that funnel users to one page. Its scaled-content policy concerns large quantities of low-value content created primarily to manipulate rankings, regardless of how the content was produced. Neither definition establishes that every city page violates policy.
For an existing page, examine its purpose and usefulness to the visitor. A review that stops at the presence of a town name cannot establish a violation. At the same time, changing a few place names across substantially similar pages does not address the doorway concern described in Google’s policy. The work is to evaluate the page against the definition, rather than assume a whole category is safe or prohibited.
Business Profile compliance is a separate check. Google identifies relevance, distance and prominence as local-ranking factors; the introductory summary on its guidance page uses “popularity.” Complete information, verification, accurate hours, reviews and relevant links are discussed. Google also says businesses cannot request or pay for better local ranking. A payment to a provider should therefore be understood as payment for work, not the purchase of a ranking from Google.
For service-area settings, Google permits up to 20 areas specified by cities, postal codes or other areas. The overall boundaries generally should be within about two hours’ driving time of the business base. If customers are not served at the business address, remove the displayed address. These are profile rules to check directly, not evidence that August specifically targeted your service-area settings.
Address eligibility needs the same care. A rented mailing address where the business does not operate is ineligible. A coworking office requires clear signage, customer reception during business hours and staffing by the business’s own staff. The question is whether the location meets those conditions, not simply whether a mailing address exists.
Review requests also have clear boundaries. Google permits sharing a review link or QR code. It prohibits incentives for posting, changing or removing reviews. Check the way requests are made as part of ordinary profile maintenance. Do not treat a review campaign, citation order or address change as a demonstrated cure for the August rollout.
BrightLocal’s Local Consumer Review Survey 2026 gives useful context for the customer journey. Published February 11, it used a representative panel of 1,002 US adults through SurveyMonkey. It found that 97% read local-business reviews and 41% always read them, compared with 29% in 2025. These are self-reported behaviors across local businesses, not findings about the August update or a home-services-only sample.
Google remained part of that behavior: 71% said they used Google for reviews, compared with 83% in 2025. That change does not measure a ranking loss or show what happened to your own customers. It describes where respondents said they looked for reviews.
The survey also connects reviews with further investigation. After positive reviews, 54% said they checked the business website. Overall, 66% did more research, compared with 34% making a purchase or booking. A positive review encounter therefore should not be counted automatically as a completed job. The stated next step and the eventual outcome are different measurements.
For an independent service business, this supports checking both the profile and the website when business results change. A profile report alone does not describe the full path to a booking, and a website ranking chart alone does not describe all review activity. Use the survey as context for keeping those records together, while measuring your own outcomes directly.
It does not show that adding reviews reverses a spam-update loss, that website visits convert at a particular rate or that every local trade follows the same pattern. Those would require different evidence. Keep review-request practices within Google’s rules and assess website changes against the pages and queries actually affected.
| Reported behavior | 2026 |
|---|
There is no Google-published August update recovery price or standardized recovery package. General SEO surveys and vendor subscriptions can help you compare a proposal, but they describe different purchases. A monitoring subscription, citation submission and managed SEO service should not be treated as interchangeable recovery products.
Ahrefs’ survey, updated August 15, 2024, covered 439 respondents. Its local SEO comparison reports an average of $1,557 per month, with agencies at $1,819 and freelancers at approximately $1,150. The most common local hourly range was $75–$100. These are survey figures, not a current quote for a US home-services business.
The regional US/Canada findings cover SEO generally: 79.1% charged at least $1,001 per month, and 66.7% charged $75–$200 per hour. Those regional figures should remain separate from the local-market averages. The detailed local comparison sits within a broader international survey.
BrightLocal’s own pricing page, viewed October 17, 2026, provides concrete one-location subscription amounts. Track is $41 with monthly billing or $369 annually. Manage is $54 monthly or $485 annually. Grow is $65 monthly or $584 annually. The page displays annual monthly equivalents of $31, $40 and $49 respectively; these are rounded displays, while the annual totals are the stated billing amounts.
The platform advertises ranking monitoring for up to 100 keywords and four competitors per location. Track advertises geo-grid visualization for up to five keywords. A 14-day trial requires no card. These limits help define what you can monitor; they do not establish that the platform can identify the cause of a loss or guarantee recovery. BrightLocal separately lists a Managed SEO Service at $1,299 per month.
Citation Builder has another pricing structure. The standard charge is $3.20 per site. The $2-per-credit amount requires bulk packages of 500, 1,000 or 2,000 credits, with one credit buying one submission. Simply Listings access is free, while citations are purchased separately. Compare the purchase size and conditions before treating a headline “from $2” amount as the cost of a small campaign.
For a proposal tied to August, ask what work the fee covers and which recorded problem it addresses. The published prices below establish costs and limits. None establishes a standard repair bill or an expected amount of recovered revenue.
Software ratings can help you assess a service, but they are not evidence that it reverses Google-update losses. The rating platform, review count and observation date belong together. Counts displayed on a vendor badge can differ from the platform’s own page without giving you a basis to infer which customers recovered rankings.
For a vendor-led comparison, BrightLocal’s own pricing-page badges showed G2 at 4.6 with 228 reviews and Capterra at 4.8 with 281 reviews on October 17. The same page showed Google at 4.8 with 366 reviews and Trustpilot at 4.6 with 752 reviews. Badge refresh dates were not displayed, and the Google and Trustpilot totals were not independently verified on those platforms.
The platform observations differ slightly: G2’s seller page showed 4.6/5 from 230 reviews, while Capterra’s review-page search extract showed 4.8/5 from 283 reviews. The Capterra extract said it was updated September 28, 2026; direct retrieval of the page failed. Gartner Peer Insights showed 4.3/5 from 13 ratings. Its product information was updated October 13, 2025, and a visible review was dated June 2, 2026.
Use the vendor’s own displayed figures when describing its badges, while preserving these differences. Do not combine counts across platforms into a recovery score or describe a rating as proof of a specific August outcome.
| Location | Rating | Count | Date and qualification |
|---|---|---|---|
Much of the apparent disagreement comes from timing. An article written August 6 or checked August 10 could accurately describe the absence of a confirmed rollout at that point. It cannot establish that no update occurred later in the month. A page focused on August 1–6 also needs a clear boundary before its conclusion is applied to August 18–21.
Other differences concern the system being discussed. Search rankings, Discover complaints, analytics problems and Ad Manager disruption are not interchangeable evidence. Search Engine Watch’s August 6 account reviewed 88 visible posts and comments and separated different complaint types. That is useful contemporary context, but those anecdotes do not form a representative business-impact study.
Commercial interpretations need a similar distinction. Local Citation Services discusses doorway pages, town-name blocks and directory links while also selling citations. Its September 2 article acknowledges uncertainty over local targeting and does not supply a representative local impact dataset. A policy interpretation can guide a check, but it should remain distinguishable from Google’s announcement of what happened.
The most detailed ranking-impact account here is Search Engine Land’s August 27 report. Its value is the disclosed sample, comparison dates, rates and measurement limits. Even that account does not measure Maps, booked jobs or causal spam violations for individual sites. The table below keeps those limits attached to each account rather than treating every prominent result as an equivalent explanation.
| Page or publisher | Coverage | Date or qualification |
|---|---|---|
The unresolved issue for independent US service businesses is measured local impact. The large keyword comparison shows unusually severe organic ranking losses in its sample. Google provides policy definitions, rollout dates and measurement guidance. Neither supplies a universal explanation for your business, an August Maps-loss rate or a guaranteed repair schedule.
A defensible decision starts with a written account of the decline: its start date, affected Search Console pages and queries, separate profile-interaction trends, and actual call or booking outcomes. That record gives you something concrete to evaluate before buying work. It also helps distinguish a general maintenance proposal from a response to a documented problem.
If a page appears to violate a spam policy, the proposed change should explain the issue in the policy’s terms. If the concern is profile eligibility or service-area accuracy, address that rule directly. If the evidence only shows a ranking change, keep the explanation at that level until further checks support a cause.
The same discipline applies to spending. A free Business Profile, a paid monitoring plan, citation submissions and managed SEO have different purposes and prices. Compare the stated work, limits and billing conditions. A survey average or software rating cannot establish what your business needs, and a rollout date cannot establish what a provider can recover.
Keep evaluating progress against the same measurements you used to establish the decline. Google says spam-policy improvements can take months to be recognized by automated systems. That is a reason to maintain a clear record of changes and outcomes, while treating promises of a fixed recovery date as unsupported by Google’s published guidance.
Takeaway
Google confirmed an August 18–21 spam update, not an August core update. Check website losses, profile interactions and actual bookings separately before paying for recovery work; the published organic study does not measure local-business losses.
Establish the event
Google’s incident record
Use the official August dates and global scope to check the timing of your decline. Include the completed September rollout when examining later changes, while keeping date alignment separate from proof of a cause.
Find the business impact
Search Console, Business Profile and business records
Examine affected pages and queries, then compare profile call-button clicks and website clicks with actual calls and bookings. These measurements describe different stages and should remain separate in any report.
Choose work with a defined purpose
Policy review and clearly priced services
Inspect city-page usefulness, profile eligibility and review practices against Google’s rules. Compare monitoring, citation and managed-service charges by their stated work and limits; neither ratings nor survey averages establish a recovery result.
Questions
Keep reading
Vendor pages change. Figures are as published on the capture date; confirm before deciding.
August 21, 2026, 01:49 PDT
History rounds the duration to 2 days, 16 hours |
Early-August windows | No confirmed ranking update listed for August 1–6 or August 12–13 | No named rollout in those windows; rankings need not have been static |
Preceding listed core update | Began May 21, 2026 | Separate from the August spam event |
September spam update | September 24, 09:15 PDT, to October 8, 01:00 PDT | Completed; history duration 13 days, 16 hours |
Impact disclosure | No query percentage, local loss rate, Maps figure or targeted-tactics list | The announcement cannot diagnose an individual business |
| Measure | August comparison | Baseline | Interpretation and limit |
|---|
Previously top-10 URLs falling beyond position 100 | 16.71% | 9.2% | Search Engine Land reports an 82% increase, approximately 1.8 times baseline; not a business penalty rate |
Entries into positions 1–3 from outside the top 20 | 12.86% | 11.5% | Reported as a 12% relative increase; not a first-position rate or a 12-point increase |
Keyword sample | 100,000 US keywords | 20 industries | Organic web results; no local-pack impact estimate |
Comparison dates | August 17 versus August 22, 2026 | July 26 versus July 31, 2026 | A before-and-after comparison, not an individual-site causal diagnosis |
Tracking boundary | Positions 1–100 | Same tracking limit | Cannot distinguish deindexing from a fall below position 100 |
SE Ranking’s own 2026 post and Search Engine Land’s August 27, 2026 report. The SE Ranking post displayed “1mo” when accessed October 17, without an exact publication date.
| Record |
|---|
| What to examine |
|---|
| What it does not establish |
|---|
Search Console | Website queries, URLs, countries, devices and search appearances | Completed calls, booked jobs or a confirmed spam violation |
Business Profile Calls | Clicks on the profile’s call button | Connected or answered calls |
Business Profile website clicks | Clicks on the profile’s website link | Website conversions or booked work |
Business call and booking records | Actual call and booking outcomes | The ranking system responsible for a change |
SE Ranking keyword study | Organic URL positions in its sample | Maps losses or the percentage of local businesses affected |
Definitions follow Google’s Search Console diagnosis and Business Profile performance guidance, accessed October 17, 2026.
| Step | Concrete check | Record to keep |
|---|---|---|
1. Establish timing | Compare the decline’s start with confirmed rollout dates | Separate start dates for website, profile interactions and business outcomes |
2. Check the longer pattern | Use 16 months of Search Console data for seasonality | The periods being compared |
3. Locate the website loss | Examine queries, URLs, countries, devices and search appearances | Affected pages and query groups |
4. Compare profile activity | Review call-button and website-link clicks separately | Interaction trends with Google’s metric definitions |
5. Verify business impact | Compare actual call and booking records | Completed outcomes rather than inferred jobs |
6. Review compliance | Inspect page usefulness and relevant spam policies | Specific issues and changes made |
7. Assess progress | Allow for Google’s months-long compliance reassessment guidance | Observed changes without a guaranteed recovery date |
Based on Google’s traffic-drop, spam-update, core-update and Business Profile documentation. These checks organize an investigation; they do not establish causation by themselves.
| Area | Google’s guidance | Useful owner check |
|---|---|---|
City and regional pages | Doorway examples include substantially similar pages and pages funneling visitors to one destination | Assess each page’s purpose and usefulness |
Scaled content | Large quantities of low-value content made primarily to manipulate rankings, regardless of production method | Review value and purpose rather than assuming a creation method decides compliance |
Local ranking | Relevance, distance and prominence; introductory summary says popularity | Check complete information, verification, hours, reviews and relevant links |
Service areas | Up to 20; overall boundaries generally within about two hours’ driving time | Check listed areas and whether the address should be displayed |
Virtual and coworking offices | Mailing-only addresses are ineligible; coworking locations have signage, reception and staffing conditions | Verify actual operations and eligibility |
Reviews | Review links and QR codes permitted; incentives prohibited | Inspect how customers are asked to post or change reviews |
Google spam policies, local-ranking guidance, service-area guidance, representation guidelines and review guidance, accessed October 17, 2026.
| 2025 comparison or limit |
|---|
Read local-business reviews | 97% | Across local businesses |
Always read reviews | 41% | 29% in 2025 |
Use Google for reviews | 71% | 83% in 2025 |
Check the website after positive reviews | 54% | A reported next step, not a conversion rate |
Do more research | 66% | Compared with 34% purchasing or booking |
BrightLocal Local Consumer Review Survey, February 11, 2026: representative panel of 1,002 US adults via SurveyMonkey. Self-reported behavior; not an August-update impact study.
| Service or plan | Published amount | Conditions and limits |
|---|---|---|
Google Business Profile | Free | Free to create and list a business |
Local SEO survey average | $1,557/month | Ahrefs survey; not a current US home-services quote |
Local SEO agencies | $1,819/month | Survey average |
Local SEO freelancers | Approximately $1,150/month | Survey figure |
Most common local hourly range | $75–$100/hour | Local-market survey comparison |
US/Canada SEO generally | 79.1% charge at least $1,001/month; 66.7% charge $75–$200/hour | Regional findings are broader than local SEO |
BrightLocal Track, one location | $41/month; $369/year | Annual display equivalent: $31/month |
BrightLocal Manage, one location | $54/month; $485/year | Annual display equivalent: $40/month |
BrightLocal Grow, one location | $65/month; $584/year | Annual display equivalent: $49/month |
BrightLocal monitoring | Up to 100 keywords and four competitors per location | Track geo-grid visualization: up to five keywords |
BrightLocal trial | 14 days | No card required |
BrightLocal Managed SEO Service | $1,299/month | Separately published managed-service charge |
Citation Builder standard | $3.20/site | Small-campaign standard price |
Citation Builder bulk | $2/credit | Packages of 500, 1,000 or 2,000; one submission per credit |
Simply Listings | Free access | Citation purchases are separate |
Ahrefs survey updated August 15, 2024, with 439 respondents; BrightLocal vendor pricing and help pages accessed October 17, 2026. Annual monthly equivalents are rounded; use annual totals for billing comparisons.
BrightLocal pricing badge: G2
4.6 |
228 reviews |
Seen October 17, 2026; badge refresh date absent |
G2 seller page | 4.6/5 | 230 reviews | Seen October 17, 2026 |
BrightLocal pricing badge: Capterra | 4.8 | 281 reviews | Seen October 17, 2026; badge refresh date absent |
Capterra review-page extract | 4.8/5 | 283 reviews | Extract updated September 28, 2026; direct retrieval failed |
Gartner Peer Insights | 4.3/5 | 13 ratings | Product information updated October 13, 2025; visible review June 2, 2026 |
BrightLocal pricing badge: Google | 4.8 | 366 reviews | Vendor badge; platform total not independently verified |
BrightLocal pricing badge: Trustpilot | 4.6 | 752 reviews | Vendor badge; platform total not independently verified |
Accessed October 17, 2026. Vendor badges and platform observations are kept separate. These software-service ratings do not measure recovery from Google updates.
FlashCrafter: “What Actually Happened and What’s Panic” |
Confirmed timeline, early volatility, local-business distinctions, costs and data limitations |
Captured October 1, 2026. September rollout status is stale after October 8 completion. Its statement that impact figures were reachable only through secondary summaries is outdated: SE Ranking’s own post and the original Search Engine Land report are accessible. |
SeeIndie: “Is there one in August?” | Search extract discusses early-August volatility, reporting problems and the author’s own site changes | Extract checked August 10, before the announcement. Full URL redirects to a private page; full current content could not be assessed. |
PalVDM: “Update, Bug, or Coincidence?” | Early-August trackers, mixed systems and diagnostic discipline | August 21, 2026. Focuses on August 1–6; whole-month no-confirmation wording conflicts with Google’s August 18 announcement. |
Something Inc: “What Google Actually Confirmed” | Separates early-August ranking volatility, Ad Manager disruption and analytics complaints | Exact publication date not established. Quantified dashboard window is August 1–6; inspected coverage lacks a complete August 18–21 account. |
Search Engine Watch: “What we know” | Reviews 88 visible posts/comments, separates Search, Discover and measurement complaints, and recommends technical checks | August 6, 2026. Predates the rollout; anecdotes are not a representative impact study. |
Local Citation Services: “What It Means Locally” | Confirmed dates, doorway pages, town-name blocks, directory links and uncertainty about local targeting | September 2, 2026. No representative local impact dataset; also sells citations. |
Search Engine Land: ranking-impact report | Sample, comparison dates, measured changes and explicit study limitations | August 27, 2026. Does not measure Maps, booked jobs or individual-site causal violations. |
Koira: “August 2026 Core Update” | Title labels the event a core update | Full retrieval failed; body not assessed. Title conflicts with Google’s published August event name. |
Pages returned prominently for the exact query and close variants in the October 17, 2026 session. Returned positions are not a reproducible US Google ranking report. Coverage judgments are limited to inspected material.