How to deal with rel=canonical when using POST parameters

[mjk26]

Hi there,
I currently have a number of URLs throughout my site of the form:

https://www.concerthotels.com/venue-hotels/o2-academy-islington-hotels/256133#checkin_4-21-2024&checkout_4-22-2024&rooms_1&guests_2&artistid_15878:256133

This sends the user through to a page showing hotels near the O2 Academy Islington. Once the page loads, my code looks at the parameters specified in the # part of the URL, and uses them to fill in a form, before submitting the form as a POST. This basically reloads the page, but checks the availability of the hotels first, and therefore returns slightly different content to the "canonical" version of this page (which simply lists the hotels before any availability checks done).

Until now, I've marked the page that has had availability checks as noindex,follow. But because the form was submitted with POST parameters, the URL looks exactly like the canonical one.

So the two URLs are identical, but due to POST parameters, the content is slightly different. Does that make sense?

My question is, should both versions of this page be marked as index,follow?

Thanks
Mike

[Moazamwriter]

Handling rel=canonical with POST parameters indeed demands careful handling. Distinguishing content variations and marking the primary version, like showcasing hotels without availability checks, as canonical aligns with SEO principles, ensuring search engines prioritize the main version for enhanced search performance. It's like optimizing web content as intricate as selecting the perfect design from a Mardi Gras PNG collection for a vibrant online presence.

[WorldICTown]

waiting a good reply and i also facing this issue. checking my website

[WorldICTown]

waiting a good reply and i also facing this issue. checking my website

[WorldICTown]

waiting a good reply and i also facing this issue. checking my website

[Jiyaroydm]

@mjk26 Handling rel=canonical with POST parameters requires careful consideration. Despite identical URLs, the content differs due to the POST parameters. It's wise to mark both versions as index,follow, given Google's focus on user signals. For clarity, let's consider an example: Say, you have a page showcasing hotels near Premier Inn London Angel. One version lists hotels, while the other checks hotel availability before listing. Mark the version without availability checks as canonical to signify its primary content. This ensures search engines prioritize the main version while still acknowledging the alternate content. This approach aligns with SEO principles and enhances search performance.