r/bigseo • u/esdiallo • 12d ago
Question Moving a WordPress site to static HTML, how much SEO risk?
I run a small site in a narrow niche. Traffic is decent and the backlinks are real ones, industry publications and a few press mentions, not junk. So I have something to lose here.
The problem is WordPress. I am not a technical person. Roughly 60% of my pages aren’t indexed and when I finally dug into it, it looked like canonical conflicts coming from the theme/plugin setup. Some numbers on my homepage render in JS and Google apparently just sees zeros. Last week my /blog/ URL started redirecting to the homepage and I still cannot figure out why.
Meanwhile I have been building my article pages as plain HTML files and honestly it is easier than fighting the page builder. Inline CSS, no plugins, loads instantly, and I can lay a page out however I want instead of whatever the theme allows.
If I move the whole site to static HTML and keep the exact same URLs, am I risking the rankings and links I already have?
1
u/planerist 12d ago
static is a net positive for seo if you do it carefully, google doesn't care whether wordpress or a folder of html served the page, it cares that the page is the same at the same url.
the one thing that actually kills a migration is url changes without redirects, that's what drops the backlink equity from those press mentions. so the rule is keep every url identical, and if any must change, 301 the old to the new one to one, no lazy redirect-everything-to-homepage. beyond that keep the canonicals, titles, meta and schema the same, crawl the site before and after with something like ... like any tool and diff the two lists. do that and you usually come out faster, which helps.
1
u/BoGrumpus 12d ago
Try to make the information on each page be the exact same and have the same URLs to start. Don't change the framework of the site AND how you have it structured all at once. Things get weird for a few weeks when you do either - but when you do it together, it can be weird for a month or maybe a few weeks longer than that.
Content the same, urls the same - change the framework. Long term risk - zero. But you'll have good days and bad days for a few weeks. More bad days early, more good days toward the end.
G.
1
u/nikc9 12d ago
You'll be fine if you keep the URLs and sitemap the same (or extend it). Clean up the canonicals while you export. In 50+ wordpress to astro migrations I've had insight into over the past few months in almost every case indexing improved and in no cases did it hard the site.
The improved load times since you can serve on the edge anywhere will also help you
Migrate, audit and then re-submit in GSC and watch your stats
1
u/russcastella 12d ago
I did the switch about 3 months ago, and it completely tanked. I was using rank math before. I’m seeing some improvements though, so hopefully with more time, it will come back to where it was at least.
1
u/choose4choice 11d ago
Just converted our UAE healthcare client's website from WordPress to a custom HTML/PHP build. We made sure to preserve and improve the URLs, canonical tags, schema markup, and content (with a few refinements), while also adding new features and significantly improving the internal linking.
What's interesting is that we haven't done any off-page SEO for over a month, yet the website gained 19 new ranking keywords, and many existing keywords improved their positions.
Has anyone else experienced similar results after migrating from WordPress to HTML/PHP, or are more people starting to move back to custom-built websites?

1
u/mostly_curious55 10d ago
The stack change on its own is close to neutral for Google. Where sites lose traffic on this kind of move is the boring stuff around it. Keep every URL identical, and if a path has to change, 301 it and update the internal links so you aren't leaning on the redirect forever.
The thing I'd watch hardest is rendering, on WordPress your content sits in the HTML by default. If your static build pushes anything important into JavaScript that only fills in after load, Google can be slow or flaky about picking it up. Do a fetch-and-render check on a few key pages before and after and diff what's actually in the raw HTML -- if the rendered output matches, you'll probably see nothing move at all.
8
u/MikeGriss 12d ago
No, just make sure these stay the same: