# in the url

[Zolddino]

Hello!

If the URLs of the pagination pages on my website look like this:
https://mysite.com/category#page4
Could this cause any indexing or crawling issues?

I've read that Google doesn't read the part behind the # in the URL, so I'm thinking it might not see the pagination pages and could perceive the products on those pages as orphaned.

What do you think?

 

[Steptoe]

In my experience they won't follow urls dynamically written with a hash #. I take it your paginated pages are created via a javascript call? Better to see if your CMS will create either static pages or accept /category/page4 type urls instead. Otherwise you'll be needing to create more internal links to your products from other pages, though you could argue that you should be doing this anyway and not relying on paginated pages as the only link to a product.

 

[Zolddino]

In my experience they won't follow urls dynamically written with a hash #. I take it your paginated pages are created via a javascript call? Better to see if your CMS will create either static pages or accept /category/page4 type urls instead. Otherwise you'll be needing to create more internal links to your products from other pages, though you could argue that you should be doing this anyway and not relying on paginated pages as the only link to a product.

Thank you for your response! What do you think could be negative impact if I change the URLs of the pagination pages, avoiding the current '#' solution? I'm concerned that this might result in a sudden influx of URLs into Google's index, potentially harming the website's rankings.

It's a relatively large website with around 10,000 products, and I'm unsure how the products could receive links from other sources. There isn't much search volume for the product names (bicycles and parts); usually, people search for the categories.

 

[Steptoe]

Thank you for your response! What do you think could be negative impact if I change the URLs of the pagination pages, avoiding the current '#' solution? I'm concerned that this might result in a sudden influx of URLs into Google's index, potentially harming the website's rankings.

It's a relatively large website with around 10,000 products, and I'm unsure how the products could receive links from other sources. There isn't much search volume for the product names (bicycles and parts); usually, people search for the categories.

If you're worried about the influx of urls, you could noindex any pagination from the 2nd page onwards. For internal linking to your products, you could have 'related products' sections on each product page, or blog posts discussing groups of products, sprinkled with links to products that are most profitable and need an indexing/ranking boost.

 

[code API]

The best practice is to noindex paginated pages. Put important content on the first page to help search engines understand as it makes for topical relevance.

Most SEO plugins would noindex dynamic pages like that by default anyway. But you should double-check.

 

[GoogSEO]

In google help it is written that you should not do so, and as a last resort you should use the parameters ?page=1 and so on (although google no longer recommends and use them, recommends a direct url like: page-1.html, page-2.html).
There can be no problems, because now he does not pay attention to your pages, but if you change them, will begin to pay attention.

He will realize that this is pagination, such pages have a very low weight and very poorly ranked.

 

[SEO Insulin]

Hello!

If the URLs of the pagination pages on my website look like this:
https://mysite.com/category#page4
Could this cause any indexing or crawling issues?

I've read that Google doesn't read the part behind the # in the URL, so I'm thinking it might not see the pagination pages and could perceive the products on those pages as orphaned.

What do you think?

Hey there!

So, about those URLs on your website like "https://mysite.com/category#page4" – using the hash (#) in URLs can be a bit tricky for search engines. Google tends to ignore the part after the # when crawling, which might pose an issue for proper indexing.

You see, search engines usually see the fragment as an anchor within a single page rather than a separate page. This could mean that your pagination pages might not get the attention they deserve, and Google might not pick them up correctly.

To play it safe and ensure your pagination pages are well-indexed, it's better to stick with more conventional URL structures, like using parameters or paths for pagination. This way, you're giving search engines a clearer signal about the organization of your content, which can improve visibility in search results.

Long story short, while the # in URLs might work for some things, for pagination, it's usually better to go with the tried-and-true methods for smoother sailing in the vast sea of search engine indexing.

 

[Zolddino]

Thank you all, mates!

 

[hideath]

Thank you for your response! What do you think could be negative impact if I change the URLs of the pagination pages, avoiding the current '#' solution? I'm concerned that this might result in a sudden influx of URLs into Google's index, potentially harming the website's rankings.

It's a relatively large website with around 10,000 products, and I'm unsure how the products could receive links from other sources. There isn't much search volume for the product names (bicycles and parts); usually, people search for the categories.

Google bots are not crawling neither indexing your pagination pages,
So, for Google, these pages doesn't exist at all, their simply a variation of the "https://mysite.com/category" page,
So is the canonical tag as well, so only that page is known, neither the internal links in the pages are fetched,

You can safely add these pagination pages if your CMS allows you to,
These pages will be treated as brand new, get crawled and fetched normally,

You might want to add a noindex or/and canonical tag to the main category to avoid getting them indexed (causing duplicate content problems),
This will allow them to get crawled, pass link juice without getting into the SERPs