Member Avatar for Aditya_26

My website was built with Angular JS 1 (not a wordpress site) . When i posted some website posts within same day. So ,When ever i checked my website on Google SERP (site:example.com), identified some of pages are crawled within 24hrs and some of pages within 1 week and some of pages with in 1 month and some of pages not cralwed . My Question is why this was happened?

Edited by happygeek because: moved
  • 2 Contributors
  • 1 Reply
  • 366 Views
  • 15 Hours Discussion Span
  • Latest Post Latest Post by rproffitt

Dani AI

Generated

For : uneven crawl timing is common for AngularJS 1 sites because Google first fetches the HTML shell, then queues pages for rendering and indexing. Pages that produce visible HTML quickly, have strong internal links, or are in your sitemap tend to be discovered and crawled sooner; others wait in the render queue or fall lower in crawl priority (crawl budget). As hinted, this is a frequent SEO question, but the root is usually rendering + discovery, not a single bug. (developers.google.com)

Diagnostic checklist (do these in order):

  • Use Search Console > URL Inspection > TEST LIVE URL and compare the rendered HTML to your expected content; that shows what Google actually saw. (developers.google.com)
  • Confirm you are not blocking JS/CSS in robots.txt and that internal navigation uses real anchor tags (<a href="...">). (developers.google.com)
  • Make sure important pages appear in an XML sitemap and submit it to Search Console. (developers.google.com)

Quick server check (run from your machine):

curl -A "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" -L https://example.com/your-page

If the curl output lacks the content you expect, Google’s initial crawl sees an empty shell.

Fixes to consider: serve pre-rendered HTML (SSR or static generation) for landing pages so crawlers see full content; dynamic rendering (pre-render for bots) is a temporary workaround but not ideal long-term; avoid hashbang (#!) routing — use the History API and server rewriting for SPA routes. For background on dynamic rendering and the older AJAX scheme, see Google’s guidance. (developers.google.com)

Next steps: pick one problem page, run the URL Inspection live test, fix rendering/linking, submit the URL for indexing, and check Crawl Stats and your server logs for Googlebot activity. Be patient — indexing can still take days to weeks depending on crawl budget and site signals. (developers.google.com)

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.