How do we fix a hidden text and keyword stuffing manual action?

Start with the notice in the Manual Actions report . Save its exact wording, affected scope, examples, and date. An audit tool reporting hidden elements does not establish that Google has applied this action. If the report is clear, use our manual action versus algorithmic decline guide to choose the investigation.

We keep two questions separate in the working record: which text is difficult to see, and which text has no credible purpose for the reader? A collapsed delivery panel may be helpful. An invisible paragraph repeating locations and services may be a manipulation attempt. Those findings need different decisions even if both appear as hidden elements in a crawl.

An accordion is not inherently a hidden-text violation. Google's hidden text policy expressly allows interface patterns such as tabs, accordions, tooltips, and text intended for screen readers when they serve users. It distinguishes those from content concealed to manipulate search engines.

For each disputed component, we test whether the control is discoverable, whether it opens the promised information, and whether the information is useful in that context. We also check mobile and keyboard access. This is our usability verification, not a claim that Google requires a particular accordion implementation. Do not delete accessibility labels merely because they are absent from a screenshot.

An acceptable container does not make every message inside it acceptable. A tab containing a product specification serves a reader; a tab containing repetitive search phrases still needs editorial review. We assess content and interaction together. Our preferred fix keeps the useful control and removes the manipulative contribution; forcing everything open can make a long mobile page harder to use without solving the editorial issue.

Build a small audit record for each suspicious fragment: page URL, exact text, screenshot, element or CMS field, display behavior, and the rule that creates it. Inspect the page as a logged-out visitor and compare desktop and mobile layouts. If the problem appears only after a script loads or under a particular condition, record that condition so another person can reproduce it.

We then search for the same fragment or generating rule across templates and content records. A footer added to every service page is a different repair from one manually edited paragraph. The useful unit of work is the repeated cause, with example pages proving that the repair reached the output. Fixing only the screenshot that triggered the investigation can leave the source intact.

If content changes according to the visitor or crawler, move into a cloaking investigation . If nobody authorized the text or script, also follow the security-issue triage . Do not assume every suspicious fragment came from the editorial team.

We rewrite each field for its actual job. A page title should identify the page; image alt text should communicate the image's relevant meaning. Google's title guidance advises against repeated keywords, and its image guidance warns against stuffing alt attributes with keywords.

A practical test is to read the field without the search brief. Does it describe this page or image accurately? Would a person using a screen reader learn something useful? If a field simply cycles through services, towns, and near-identical phrases, we replace it with a description based on the actual content. We also correct the import or generation rule so the next publication does not restore it.

We do not aim for an invented keyword-density target. Product names, technical terms, and place names may recur naturally. The editorial decision is whether the repetition contributes meaning. A word counter can locate an unusual pattern; it cannot determine whether a manual action has been resolved. We ask a reviewer to explain what each phrase contributes before looking at density. That makes the decision reproducible without inventing a numerical threshold.

For useful information concealed by a broken presentation rule, restore an understandable way to reach it. For text written only to target searches, remove it or replace it with information the page genuinely needs. Making a manipulative keyword block visible does not automatically turn it into helpful content.

We keep a disposition for every repeated pattern: retained with an explanation, rewritten, or removed. Each decision should name the source that changed and a representative live page. That gives the team a reviewable boundary: the delivery accordion was preserved because it answers delivery questions; the generated city list was removed because it added no location-specific information.

Our evidence packet pairs the original behavior with the corrected output and explains how the same fix was applied elsewhere. It should be possible to follow the chain from notice to source rule to live verification without reading a long narrative. Include any exceptions still under investigation internally; unresolved patterns are a reason to continue the work.

Follow the action-specific instructions in Google's Manual Actions documentation and use our reconsideration request guide to organize the submission. If a previous submission failed, compare the new evidence against the rejected-request checklist . For help coordinating the audit, implementation, and evidence, our manual penalty recovery work brings those responsibilities together.