Excluded by ‘noindex’ tag – Error on GSC on homepage

Hi again!

As for the first issue, I can confirm Google hasn’t indexed the homepage (they did other pages), but I can also confirm that there’s currently no noindex tag present on the homepage — this is good.
It is likely that Google has cached a broken copy of the homepage, and needs to recrawl the page again. Please see if you can inspect the live URL and request (re)indexing: https://support.google.com/webmasters/answer/9012289?hl=en#request_indexing.

For the second issue, the /contact-us page redirects to /contact-us/ (with a / at the end). This is fine; good, even. What isn’t fine is that they experienced a redirect error from the non-slashed page. I couldn’t find any indexing issues with the real /contact-us/ page.
This was 4 days ago (their timestamp is 7 Jul 2023, 23:02:03 your local time), 2 days before you opened this request. Do you remember having TSF active at that point, or that the server the website is hosted on was experiencing issues? Try inspecting the live URL as described in the link above and see if the error still occurs; Googlebot experiences a fluke once in a while.

Hello,

First of all, thank you for your detailed response with clarification on each point. Really helpful.

Yes, There was No noindextag on the homepage. And you are right, that ?Google likely might have cached a broken copy of the homepage or some previous one. I have already requested re-indexing, and not it is successful and not throwing this error.

Regarding Contact Us page-
First of all, I could not understand from where Google is reading this /contact-us that is without the slash at the end of “us” text.
As I think the URL is, and should be like – /contact-us/ only . Please correct me If I am wrong.
And in either case, why it is now redirecting to /contact-us/

As far as I can see the page is actually with the /contact-us/ itself. Yes, you are right, that it was of 7 Jul 23. But I already requested Indexing earlier for the page (just like homepage) thinking, that it might recorrect it and stop throwing the error.

But this is what it showed on for 10 and and a result for reindexing on 11 Jul also-
https://i2.paste.pics/2b73da974da9c5b8e1800486f66ad187.png

I am not sure about TSF plugin activation on that date (probably may be a day before or two). But as per the link shared by you, I tested inspecting both the URLs. This is what it shows for each –

for /contact-us/ page with slash at end-
https://i2.paste.pics/029048b473fa6419c5a4666cc7dabf2c.png

for /contact-us page without slash at end-https://i2.paste.pics/807e37c4ee1e3676e3ddd455aa2fba66.png

So, I am still not sure, whether to Request for Indexing for /contact-us or not. If we request for Indexing, then shall we need to mention the canonical URL somewhere or in the Contact Us page settings, to avoid this error.

Or shall we leave it as it is. If we leave it, will it keep throwing the error for /contact-us or not.

Regards

Hello!

Sorry, in scouting old posts, I see I missed your follow-up.

You should ignore /contact-us and only use /contact-us/ because you’re using trailing slashes in your permalink settings (as anyone should).

I’m not sure why you’re getting the error (the redirect is valid, no broken headers), but in this image you shared, under “Discovery,” the page is neither found in the sitemap nor has a referring page (there’s no link from your site or someone else’s). The error should vanish after a while since there are no links to the page, and you can safely ignore it.