Appreciate the honesty here, especially counting out your own 4 clicks so the data stays clean.
Just a quick note on the sitemap error: GSC almost always gets stuck on "Couldn't fetch" for free .github.io URLs even when the file is completely fine. Moving to a custom domain usually fixes it instantly. In the meantime, your internal links between the 10 calculators are more than enough for Googlebot to find everything.
Will be following along for next week's update. When you connect the custom domain, are you going to redirect the old GitHub Pages URLs or just treat this first month purely as a throwaway test?
Thanks, that's really helpful, and good to know the sitemap issue is common on github.io. I'll report back on whether it clears after the move.
On your question: I'm not treating it as a throwaway. The plan is to connect a custom domain after my current week-long test finishes, let the old GitHub Pages URLs redirect to the new ones (GitHub does this when a custom domain is set, but I'll verify it before relying on it), update the canonical tags and sitemap to the new domain, and add the new property in Search Console. I'll write up how the migration goes in a follow-up post, including whether indexing improves.
Thanks for sharing the real numbers instead of a success story. The part that stood out to me was the drop after 3 Nov, from 173 impressions down to zero, and your decision to wait a week before touching the pages so you can tell cause from effect. That takes discipline when the instinct is to fix everything at once. I also liked that you counted out your own 4 clicks so the data stays honest. Looking forward to next week's update, especially what happens after the custom domain goes live.
Thanks, I appreciate that. The week of waiting is the hardest part, because every instinct says to fix something. I'll share what changed, or didn't, next week, and then what happens after the domain move.
Comment marked as low quality/non-constructive by the community. View Code of Conduct
SEO monitoring tool. Crawls your site daily or hourly and alerts you when a noindex tag, robots.txt block, sitemap error or canonical change appears. Free plan.
Thanks for sharing the part that didn't go well, most experiment write-ups stop at the peak. A 173-then-zero curve on a brand-new site with no links looks a lot like Google trying the pages out and then backing off, so waiting a week before changing anything sounds right. The one thing I'd do sooner is the custom domain: if you move off github.io after Google has started forming an opinion, the new host starts from zero again. Has the "Couldn't fetch" sitemap cleared yet, or is Google finding pages through internal links only?
Comment marked as low quality/non-constructive by the community. View Code of Conduct
On the “Crawled - currently not indexed” URLs, I’d separate that from the sitemap fetch issue: a sitemap helps discovery, but it doesn’t make Google keep a URL. After your week of waiting, compare one indexed and one excluded calculator for genuinely distinct examples and content, internal links, and the canonical Google selected. That should help distinguish thin or overlapping pages from a temporary processing issue without changing several variables at once.
Comment marked as low quality/non-constructive by the community. View Code of Conduct
Appreciate the honesty here, especially counting out your own 4 clicks so the data stays clean.
Just a quick note on the sitemap error: GSC almost always gets stuck on "Couldn't fetch" for free .github.io URLs even when the file is completely fine. Moving to a custom domain usually fixes it instantly. In the meantime, your internal links between the 10 calculators are more than enough for Googlebot to find everything.
Will be following along for next week's update. When you connect the custom domain, are you going to redirect the old GitHub Pages URLs or just treat this first month purely as a throwaway test?
Thanks, that's really helpful, and good to know the sitemap issue is common on github.io. I'll report back on whether it clears after the move.
On your question: I'm not treating it as a throwaway. The plan is to connect a custom domain after my current week-long test finishes, let the old GitHub Pages URLs redirect to the new ones (GitHub does this when a custom domain is set, but I'll verify it before relying on it), update the canonical tags and sitemap to the new domain, and add the new property in Search Console. I'll write up how the migration goes in a follow-up post, including whether indexing improves.
Now please check my Updated website
mrcalcs.com/
Now please check my Updated website
mrcalcs.com/
Thanks for sharing the real numbers instead of a success story. The part that stood out to me was the drop after 3 Nov, from 173 impressions down to zero, and your decision to wait a week before touching the pages so you can tell cause from effect. That takes discipline when the instinct is to fix everything at once. I also liked that you counted out your own 4 clicks so the data stays honest. Looking forward to next week's update, especially what happens after the custom domain goes live.
Thanks, I appreciate that. The week of waiting is the hardest part, because every instinct says to fix something. I'll share what changed, or didn't, next week, and then what happens after the domain move.
Now please check my Updated website
mrcalcs.com/
Thanks for sharing the part that didn't go well, most experiment write-ups stop at the peak. A 173-then-zero curve on a brand-new site with no links looks a lot like Google trying the pages out and then backing off, so waiting a week before changing anything sounds right. The one thing I'd do sooner is the custom domain: if you move off github.io after Google has started forming an opinion, the new host starts from zero again. Has the "Couldn't fetch" sitemap cleared yet, or is Google finding pages through internal links only?
Now please check my Updated website
mrcalcs.com/
On the “Crawled - currently not indexed” URLs, I’d separate that from the sitemap fetch issue: a sitemap helps discovery, but it doesn’t make Google keep a URL. After your week of waiting, compare one indexed and one excluded calculator for genuinely distinct examples and content, internal links, and the canonical Google selected. That should help distinguish thin or overlapping pages from a temporary processing issue without changing several variables at once.
Now please check my Updated website
mrcalcs.com/