Bug : Tour page not adjusted for mobile

[jagpreetrahi]

New Description:

please view the below comment.

[JeelRajodiya]

@jagpreetrahi We currently do not plan to support mobile design - please view this comment. However, we had a redirect screen for the mobile user which would redirect the users to a /mobile page - commit. but this was causing the Search engines to not detect our pages properly, so that commit was reverted.

We can think of adding a new logic which would redirect the users to a /mobile page (or maybe show a popup when the device is mobile) - please keep in mind to stick with the designs for the mobile pages which we had in the previous commits.

@jagpreetrahi Let me know if you like to work on this modified issue, or anyone else who is interested in working on it. Thanks,

[jagpreetrahi]

Hey @JeelRajodiya , what I have understand is if we are trying to adding a new logic for /mobile page, it might again still cause search engine issue.
So for that, a better alternative approach could be to dynamically serve the mobile content on the same page without changing the URL.
Or Instead of redirect, a pop up warning users that the site isn’t optimized for mobile and suggesting desktop usage might be a less disruptive approach.

Several SEO issue :
a. Search engine may ignore the desktop page.
b. Duplicate content issue.
c. Loss of page authority.

I'd like to work on this issue, let me know if it's possible

Thanks

[JeelRajodiya]

@jagpreetrahi The goal is to display a message that "tour is not available on mobile" without affecting indexed pages on google. You can work on it!

[jagpreetrahi]

hey @JeelRajodiya , as you mention above without affecting indexed pages on google, I have to display a message. For that,
What I am thinking is used meta tag for tell the google like this page is not mobile-friendly
(meta name="robots" content="noindex")
I read some next.js docs, and go through this Next.js , the below implement could be work by adding robots.txt file.
And add : User-agent: Googlebot
Disallow: /mobile
To prevent goggle from indexing /mobile

Looking forward for your opinion
Thanks

[JeelRajodiya]

sounds good! We can include this in the PR. However it won't resolve the underlying issue of redirecting to the /mobile page while crawling. I am not sure though. Can you think of other ways to prevent the redirection?