Google acts like I don’t exist?

serpsystems · Feb 3, 2026

I’ve already had some prior experience with WordPress gambling landing pages, and because of that I wanted to try a new approach that has been considered more beneficial for SEO by many users; Next.JS.

With the help of Claude 4.5 Opus, I made a big iGaming site, with lots of useful information, images, real wikis…
I have a problem though: The sitemap never gets considered. It is generated dynamically and works, Google reads it and discovered all the pages.

The problem is that, even after a month, Google does not index the pages. If I insert the URLs manually, it says that they doesn’t get referenced in any Sitemap, even though they do. They only get indexed if I request it.

Also, the favicon stays default… Don’t know why but every other service recognizes the favicon while Google doesn’t.

bhseoworld · Feb 4, 2026

classic nextjs growing pains . googlebot is lazy , it often skips the second pass indexing ( where it renders js ) to save compute resources . if ur content is hydration-dependent ( client-side fetching ) , the bot just sees an empty div and moves on
check ur source code ( ctrl+u ) . if u dont see the actual text of ur articles there , ur relying on client-side rendering . switch to SSR ( getServerSideProps ) or SSG immediately
re : discovered - currently not indexed
that’s usually a crawl budget / trust issue , not just technical . u spun up a big site in a high-risk niche ( igaming ) with zero history . google put u in the sandbox . sitemaps are weak signals now
if u ping the urls directly , u bypass the queue . waiting for organic crawl on a fresh nextjs gambling site is gonna take 6 months
for the favicon : make sure it’s in the /public root folder and explicitly defined in your layout.tsx metadata . nextjs weirdly caches old favicons sometimes , try a cache bust query string

Kupecdbenicn · Feb 4, 2026

This usually comes down to rendering and discovery signals: make sure your sitemap is static-accessible, linked internally, and that key pages are reachable via crawlable links (not only JS). For Next.js, also double-check SSR/headers, canonical tags, and Search Console coverage manual indexing working is a sign Google can fetch pages but isn’t confident enough to index them at scale yet.

serpsystems · Feb 4, 2026

bhseoworld said:
classic nextjs growing pains . googlebot is lazy , it often skips the second pass indexing ( where it renders js ) to save compute resources . if ur content is hydration-dependent ( client-side fetching ) , the bot just sees an empty div and moves on
check ur source code ( ctrl+u ) . if u dont see the actual text of ur articles there , ur relying on client-side rendering . switch to SSR ( getServerSideProps ) or SSG immediately
re : discovered - currently not indexed
that’s usually a crawl budget / trust issue , not just technical . u spun up a big site in a high-risk niche ( igaming ) with zero history . google put u in the sandbox . sitemaps are weak signals now
if u ping the urls directly , u bypass the queue . waiting for organic crawl on a fresh nextjs gambling site is gonna take 6 months
for the favicon : make sure it’s in the /public root folder and explicitly defined in your layout.tsx metadata . nextjs weirdly caches old favicons sometimes , try a cache bust query string

I see...
The site is a mix of Client and Server components, but the content itself is always Server-side, in fact I can see it when I check my Source Code.

What should I do then? Keep manually submitting links?

Rankmathseo · Feb 4, 2026

Totally normal with new Next.js sites, especially iGaming. Google finds pages but takes time to trust them. Check robots.txt, internal linking, and give it more time. Favicon updates are slow.

TechSavvyTess · Feb 4, 2026

Johngok said:
I’ve already had some prior experience with WordPress gambling landing pages, and because of that I wanted to try a new approach that has been considered more beneficial for SEO by many users; Next.JS.

With the help of Claude 4.5 Opus, I made a big iGaming site, with lots of useful information, images, real wikis…
I have a problem though: The sitemap never gets considered. It is generated dynamically and works, Google reads it and discovered all the pages.

The problem is that, even after a month, Google does not index the pages. If I insert the URLs manually, it says that they doesn’t get referenced in any Sitemap, even though they do. They only get indexed if I request it.

Also, the favicon stays default… Don’t know why but every other service recognizes the favicon while Google doesn’t.

I ran into similar issues when moving from WordPress to Next.js. Google often struggles with dynamically generated sitemaps unless you explicitly pre-render or submit a static version through Search Console.

torus666 · Feb 4, 2026

Johngok said:
I’ve already had some prior experience with WordPress gambling landing pages, and because of that I wanted to try a new approach that has been considered more beneficial for SEO by many users; Next.JS.

With the help of Claude 4.5 Opus, I made a big iGaming site, with lots of useful information, images, real wikis…
I have a problem though: The sitemap never gets considered. It is generated dynamically and works, Google reads it and discovered all the pages.

The problem is that, even after a month, Google does not index the pages. If I insert the URLs manually, it says that they doesn’t get referenced in any Sitemap, even though they do. They only get indexed if I request it.

Also, the favicon stays default… Don’t know why but every other service recognizes the favicon while Google doesn’t.

This is a common headache when switching to Next.js. Google is often slower to trust JS-heavy sites compared to WordPress, especially in a tough niche like iGaming.
A few things to check: make sure you’re using SSG or ISR so the bot sees the HTML immediately instead of waiting for JS to render. Also, don't just rely on the sitemap—make sure your pages are linked heavily within the actual content so the bot has a clear path to follow.
If manual indexing works, it means your pages are fine, Google just hasn't prioritized crawling you yet. As for the favicon, Google is super picky; make sure it’s exactly 48x48px or a multiple of that. Just give it more time and maybe a few quality backlinks to wake the bot up.

tenro · Feb 4, 2026

Dynamic sitemaps in Next.js can sometimes serve with caching headers or MIME types that Google doesn’t like. Check that the sitemap URL returns a 200 response, uses application/xml and is listed in your robots.txt.

bhseoworld · Feb 4, 2026

Johngok said:
I see...
The site is a mix of Client and Server components, but the content itself is always Server-side, in fact I can see it when I check my Source Code.

What should I do then? Keep manually submitting links?

manual submissions are a trap . if u do that at scale u r just wasting ur time
since u confirmed its ssr then the issue isnt technical.. its authority validation . iGaming on a fresh nextjs build is basically a red flag for the sandbox . u need to force the discovery signal
grab a few google cloud service accounts and hook them up to the indexing farm . we run a mass-pusher script for all our new p-seo fleets to bypass the standard crawl delay . it’s the only way to get thousands of pages in the index within 48h in competitive niches . manual sitemap pings are just too weak for grey niches
also check ur depth of discovery . if those wikis are buried deep in the structure the bot wont give a damn . keep everything within 2 clicks from home
one more thing we usually inject a layer of user interaction data via ga4 measurement protocol to prove to the algo that the site has a pulse . if a site exists but zero humans hit it , google defers the indexing . fix the traffic signal and the pages will stick

serpsystems · Feb 4, 2026

bhseoworld said:
manual submissions are a trap . if u do that at scale u r just wasting ur time
since u confirmed its ssr then the issue isnt technical.. its authority validation . iGaming on a fresh nextjs build is basically a red flag for the sandbox . u need to force the discovery signal
grab a few google cloud service accounts and hook them up to the indexing farm . we run a mass-pusher script for all our new p-seo fleets to bypass the standard crawl delay . it’s the only way to get thousands of pages in the index within 48h in competitive niches . manual sitemap pings are just too weak for grey niches
also check ur depth of discovery . if those wikis are buried deep in the structure the bot wont give a damn . keep everything within 2 clicks from home
one more thing we usually inject a layer of user interaction data via ga4 measurement protocol to prove to the algo that the site has a pulse . if a site exists but zero humans hit it , google defers the indexing . fix the traffic signal and the pages will stick

I’m hitting you with a DM

JJJones33 · Feb 9, 2026

google is now using a smaller pool of websites for results. So that you advertise. They control the search results and make you pay

Google acts like I don’t exist?

serpsystems

Regular Member

bhseoworld

Junior Member

Kupecdbenicn

Newbie

serpsystems

Regular Member

Rankmathseo

BANNED

TechSavvyTess

Newbie

torus666

BANNED

tenro

BANNED

bhseoworld

Junior Member

serpsystems

Regular Member

JJJones33

Newbie

Main Menu

Marketplace

Making Money

BlackHat World