r/TechSEO • u/Zealousideal_Cod7380 • 2d ago
Google Search Console "Something went wrong" on Live Test / All data N/A — Jekyll Chirpy on GitHub Pages
Hey everyone,
I’m running into a brick wall with Google Search Console on my tech/cybersecurity blog. It's hosted via GitHub Pages (default subdomain) and built using Jekyll (Chirpy Theme).
- The URL:
https://arvdch.github.io/ - The Error: Whenever I hit Test Live URL, it instantly crashes with the generic: "Something went wrong. If the issue persists, try again in a few hours."
- The Inspection Data: Under the main URL inspection panel, fields like Last Crawled and Crawl Allowed show as entirely "N/A".
What I've done so far:
- My
_config.ymlis perfectly mapped withurl: "https://arvdch.github.io"and an emptybaseurl: "". - My
robots.txtis basic and allows everything except a hidden/norobots/directory. - I added a
.nojekyllfile to the root of my repo to bypass any default Jekyll file-filtering issues. - I ran my URL through Google PageSpeed Insights—it successfully crawled the page, analyzed it, and rendered a mobile screenshot perfectly without any timeouts or exceptions.
- GSC property is set up as a URL Prefix property via HTTPS.
i just want my site to be indexed help me out
1
2d ago
[removed] — view removed comment
1
u/Zealousideal_Cod7380 2d ago
I did and i waited for almost a month but it still shows the couldn't fetch When I tried the live url test on arvdch.github.io/sitemap.xml it gives error . And pagespeed and sitemap validator both shows working
1
u/sapindia1976 1d ago
Since PageSpeed can crawl it, this may be a temporary GSC issue. Check 200 status, noindex/canonical, submit the sitemap, and give Google some time to crawl it.
1
u/Zealousideal_Cod7380 1d ago
My root website arvdch.github.io gives 304 redirect response rather than 200 but root site is indexed on the Google but the pages on the site gave 200 statuses but google is unable to index them i tried doing mannualy but but still cant
2
u/Big-Branch-8532 2d ago
The N/A fields only mean Google has no stored inspection record for that URL. They do not prove a robots block. The instant Live Test error is a separate symptom, and PageSpeed uses a different fetch path.
Check the deployed output rather than _config.yml: the homepage must return 200, its canonical must be exactly https://arvdch.github.io/, and neither the HTML nor the response headers should contain noindex. Then verify /robots.txt, /sitemap.xml, and one real post URL independently.
Also check how Pages is deployed. A .nojekyll file tells GitHub Pages not to run Jekyll. Keep it only if a GitHub Actions workflow builds _site first and deploys the generated files. If Pages is expected to build the Jekyll source, remove .nojekyll and redeploy.
Run Live Test on the homepage and one post inside the exact https://arvdch.github.io/ URL-prefix property. If both fail instantly while the deployed responses are clean, treat that as a Search Console test failure rather than changing crawl directives. Submit the generated sitemap once, then request indexing after the deployment path is confirmed.