Core Updates & E-E-A-T
Understand broad Google core updates, investigate traffic changes, and review content through the E-E-A-T lens.
On this page7 sections
What a core update is
Google makes broad changes to its search systems several times a year. A core update aims to improve results overall; it does not target an individual page or automatically mean that a site has violated a policy. Check the Google Search Status Dashboard for the actual update names, start dates, and completion dates.
Avoid attributing a traffic change to an update just because the dates overlap. Demand, competition, seasonality, indexing issues, site changes, and changes in Search appearance can also affect clicks. Google's core-update guidance recommends investigating the pattern before changing content.
Investigate a sustained drop
- Confirm the timeline. Check whether a core update actually occurred and when it finished. Google recommends waiting at least a full week after completion before comparing Search Console data.
- Compare like periods. In Search Console, compare the period after the rollout with a comparable period before it began. Account for seasonal demand and any major changes you made to the site.
- Find the affected scope. Separate Web Search from Images, Video, and News. Look at the pages and queries with the largest changes in impressions, position, and clicks.
- Check technical causes. Investigate indexing, canonicals, redirects, server errors, and accidental
noindexchanges if the loss is concentrated on particular URLs. - Assess the content. For a large, sustained drop, review whether the affected pages fulfill the searcher's task better than the alternatives now shown. Ask people outside the team to evaluate clarity and usefulness.
Small position changes do not justify a sitewide rewrite. Google's guidance cautions against quick fixes and recommends meaningful improvements that help readers. Removing pages should be a last resort when the content cannot be improved.
E-E-A-T as a review lens
E-E-A-T stands for experience, expertise, authoritativeness, and trustworthiness. It is a framework used in Google's quality guidance to assess whether content seems helpful and reliable. Google states that E-E-A-T itself is not a specific ranking factor. Do not treat an author bio, a schema property, or a backlink count as a score that guarantees better placement. See Google's people-first content guidance.
Experience and expertise
Ask whether the page shows the kind of knowledge its topic needs. Firsthand tests, original photos, methods, data, or examples can help when they are genuine and relevant. Some topics are well served by practical experience; others require specialist expertise. Explain how advice was reached instead of adding credentials that do not support the claim.
Authoritativeness and trust
Make it clear who is responsible for important content and how readers can verify it. Check factual accuracy, source quality, publication and review dates when relevant, and whether claims match the evidence shown. Fix misleading or outdated information before adding decorative trust badges.
For topics that could significantly affect health, finances, safety, or well-being, accuracy and a trustworthy basis are especially important. This is often called YMYL (“Your Money or Your Life”). Review such material with suitable expertise and authoritative sources; avoid pretending that a short universal checklist can establish expertise.
Improve the page for people
For an affected page, write down the reader's task and the evidence that the page meets it. Then prioritize changes such as:
- Correct outdated or unsupported claims and explain important limitations.
- Add original examples, observations, or data you can substantiate.
- Improve headings and navigation so the answer is easy to locate.
- Remove repetition that obscures the useful material.
- Ensure the author or organization is accurately identified where readers expect it.
- Repair broken links, missing media, and interaction problems.
Measure whether the changes help readers and whether Search Console trends improve over time. Google notes that effects can take time and are not guaranteed by any single edit.
Keep the update record current
Use the status dashboard for current rollout dates instead of a copied “latest updates” table. Its incident list distinguishes core, spam, and other updates. A dashboard entry identifies an update and its timing; it does not prove which specific page elements caused a site to gain or lose traffic.