Pre rendering, site visibilty google crawlbots

Support
1

Hello, please give me your thoughts on pre-rendering, my developer is currently trying to sell me SEO services for domain (nationalremovalandstorage1) https://nationalremovalsandstorage.co.uk/ which i am sure to engage with in the next few months anyway……however im very concerned the site has ‘dropped off a cliff’ with google search console, originally new pages were index showing unique meta data and now all of a sudden before Christmas the data has become generic such as;

National Removals and Storage
https://nationalremovalsandstorage.co.uk › house-remo…
National Removals and Storage. Please enable JavaScript to use this website. Call us: 0800 047 2607.
National Removals and Storage

National Removals and Storage
https://nationalremovalsandstorage.co.uk › office-remo…
National Removals and Storage. Please enable JavaScript to use this website. Call us: 0800 047 2607.
National Removals and Storage

National Removals and Storage
https://nationalremovalsandstorage.co.uk › packing
National Removals and Storage. Please enable JavaScript to use this website. Call us: 0800 047 2607.

I don’t understand what has changed. Ive been advised this is a pre-rendering issue and have now enabled Netlify pre-render plug and re-deployed……no changes so far, and im unsure if the site is now pre-rendered or not.

How do I test if this is effective, and if it is not, can anyone suggest the next steps?

TIA

2

The site is being deployed manually, so the pre-rendering extension would not work. But yes, your site needs prerendering and you can verify it by running the following in terminal:

curl -D - -A "googlebot" "https://nationalremovalsandstorage.co.uk/"

That should show you the HTML response for your site. In the body it only shows:

<body>
    <noscript>
      <div style="padding: 20px; text-align: center;">
        <h1>National Removals and Storage</h1>
        <p>Please enable JavaScript to use this website.</p>
        <p>Call us: <a href="tel:08000472607">0800 047 2607</a></p>
      </div>
    </noscript>
    <div id="root"></div>
  </body>

which should instead show some prerendered content if prerendering is working.

3

Thank you so much for the reply, so i have to automate deployment to have use of pre rendering? My developer is currently looking at your response.

4

Yes. You will have to use git deploys.

7

Hi, the site is now periodically deployed via GitHub. Can you take a quick look, if possible, to see if the pre-rendering issue still exists? The pre rendering extension is enabled.

8

(looks like I forgot to hit send here, so this message was still in my drafts)

It is trying to prerender now:

curl -D - -A "googlebot" "https://nationalremovalsandstorage.co.uk/"

HTTP/2 500
age: 8
cache-control: no-cache
cache-status: "Netlify Durable"; fwd=bypass, "Netlify Edge"; fwd=miss
cache-status: "Netlify Durable"; fwd=bypass, "Netlify Edge"; fwd=miss;detail=p1
content-type: text/plain;charset=UTF-8
date: Thu, 22 Jan 2026 17:02:29 GMT
netlify-vary: query
server: Netlify
strict-transport-security: max-age=31536000
vary: Accept-Encoding
x-content-type-options: nosniff
x-nf-request-id: 01KFKAGCQ2HFSGDJ2ZJPQ2Y58Y

Prerender failed.

But it’s failing. Checking the logs here: Function details | Functions | nationalremovalandstorage1 | Netlify, there are still no clear details:

image
image2194×482 133 KB