Somebody opens Search Console, sees a notice under Manual Actions, and the next four hours decide how long the recovery takes.
I have seen chains lose three months on decisions made before lunch on day one. Not because the work that followed was bad. The first day created problems the rest of the project had to unpick: deleted pages, a rushed appeal, a disavow file uploaded before anyone had contacted a single site.
So this is a post about restraint. The instinct on day one is to act, and almost everything worth doing on day one is preparation.
First, Read The Scope And Nothing Else
Before you look at a single URL, find the scope. It will say either partial match or site wide match, and the difference changes everything that follows.
Partial match means Google has applied the action to specific sections. Your guides may be untouched. Your homepage may be fine. The damage is contained, and so is the work.
Site wide match means nothing on the domain is exempt, including pages with no connection to the problem. For a chain this is the version that takes every store down on the same day. That is why the phone starts ringing before anyone in marketing has read the notice.
Screenshot the notice with the scope visible. You will need it later, and the wording sometimes changes when the action is updated.
What To Do Today
1. Preserve the evidence before it ages out. Export your Search Console performance data now, at the maximum date range. Export the Pages report. Export the links report, both the sample of linking sites and the top linked pages. Search Console data has a retention window, and a recovery that runs six months will outlive some of what you can see today.
2. Run a full crawl and save the file. Not a sample, the whole site. You need a snapshot of what existed on the day the action was live. In three months somebody will ask what a page looked like before it was rewritten, and nobody will remember.
3. Find out who has had access, going back two years. Former agencies, freelancers, the developer who built the site, the intern who was given the blog. On the link cases the answer is almost always in that list, and on the content cases it is usually a template decision nobody documented.
4. Tell the business what to expect, in writing, today. Say that recovery takes weeks rather than days, that nobody outside Google can give a timeline, and that appealing early makes it slower. Getting that sentence on the record on day one prevents the pressure that causes a premature appeal in week two.
What Not To Do Today
Do not delete pages. The instinct is to remove whatever was flagged. It feels decisive and it is the most damaging option available. Deleted pages become errors, errors at scale look like a site falling apart, and you have destroyed the evidence of what you fixed. If a page really should not exist, redirect it properly or serve a correct status code. That decision belongs in week two, not hour three.
Do not submit an appeal to see what happens. A rejected appeal is not a free retry. The next reviewer opens the case knowing the last one said no, and reads accordingly. What a denial actually costs, and the five ways requests earn one, is its own post. Read it before anyone in the building drafts a word.
Do not upload a disavow file yet. Google expects genuine removal attempts before a disavow, and a submission consisting of a disavow file with no outreach log reads as the shortcut it is. The disavow is the last step of the link work, not the first.
Do not fix only the URLs Google listed. This is the single most common reason a first reconsideration request is denied, and it deserves its own section.
Examples Are Not The List
The notice will name a handful of URLs. Eleven is a typical number. Teams read that as the scope of the problem, fix those eleven, and submit.
Those URLs are a sample, chosen to illustrate the pattern. The action applies to everything matching that pattern, and finding the full set is your job.
For a scaled content case on a chain, that usually means every location page, not the four that were named. For a link case it means every referring domain sharing the characteristics of the ones listed, not just the ones you were shown.
How to build the real list: take the named examples, identify what they have in common, then query your crawl for everything matching. If four location pages were named and they share a template, the pattern is the template, and the list is every page built from it. Write the list down as a spreadsheet with a status column. You will be asked to describe what you did, and “we rewrote the location pages” is not a description a reviewer can verify.
Then test the list before you trust it. Pick five pages that are not on it, at random, and ask whether a reviewer would flag them. If the answer for any of them is yes, the pattern was defined too narrowly and the list is not done. Chains that skip this test find out during the review instead, at the cost of a denial and a slower second reading.
The Two Cases You Are Most Likely To Have
Cannabis sites get two manual actions far more than any other, and both trace back to the same constraint: paid channels are closed, so operators lean harder on the two levers that remain.
Scaled content abuse. Location pages produced from one template across many stores. The tell is that a paragraph still makes sense with a different city dropped into it. If that describes your pages, the similarity between them is the thing to measure first, because it tells you how far the pattern spread.
Unnatural inbound links. Paid placements, networks, or an agency campaign from years ago that nobody has looked at since. The tell is a cluster of referring domains with no editorial relationship to cannabis retail, often sharing hosting, footprint, or anchor text.
It is common to carry exposure on both at once, and to receive an action for one while the other sits waiting. Fixing one and ignoring the other is how a site gets a second action three months after recovering from the first.
What The Next Few Weeks Look Like
Day one is preparation. The actual work follows a sequence, and the sequence matters more than the speed.
Inventory the whole affected pattern. Fix all of it, not the examples. Document every decision with dates, because the request is a record rather than an argument. Then submit once, and wait without submitting again. What each of those four steps actually involves is the rest of the project.
Plan for the fix itself to take over a month on a chain of any size. Stating that early is a kindness to everyone. The pressure to show progress is what pushes teams into the week two appeal, and that appeal turns a two month recovery into a six month one.
Check whether you are ready to submit
Before anyone drafts anything, the builder walks the same ground a reviewer will. Answer its questions honestly and it will either assemble the draft or tell you which part of the work is not finished yet.
Open the reconsideration request builder
On Blaming The Previous Agency
This comes up in almost every link case, and it is worth handling properly because it affects the tone of the eventual request.
You can state it once, as a fact. “These links were built by a supplier between 2021 and 2022, under a contract we have since ended.” That is useful context and a reviewer will read it as such.
What does not land is leaning on it. The site owns those links no matter whose hands built them. The stronger version acknowledges the gap directly: the work was commissioned, it was never audited, and that was the failure.
Do not promise anyone a recovery date.
Google publishes no timeline for the review queue and it cannot be hurried. If you give the business a date you will either miss it, or you will hit it by luck and be expected to repeat that next time.
Give them a sequence instead: inventory, fix, document, submit once, wait. People accept an honest process far more readily than they accept a missed deadline.
The Thing To Hold Onto On Day One
A manual action is recoverable. That is the most useful thing to know in the first hour, and it is easy to lose sight of while the traffic graph is falling.
It is not an algorithmic judgment about the quality of your business that you have to somehow argue your way out of. It is a specific finding about a specific pattern, and there is a defined process for clearing it. Sites recover from this every week.
If you would rather not run the first month alone, penalty recovery is a fixed scope project we take on, from the inventory to the reconsideration request.
What determines how long it takes is almost entirely how disciplined the first month is. Teams that inventory properly, fix everything, and submit once tend to be through it in a matter of weeks after submission. Teams that appeal early and repeatedly spend months proving they were not ready.
We see the same pattern in our cannabis SEO consulting work: the first month decides the timeline more than the size of the problem does.
If you take one thing away
Do nothing irreversible today. Read the scope, preserve the evidence, find out who had access, and tell the business the truth about the timeline.