I have 2 websites, both use a single-page app framework. One uses React, and one uses Angular. Neither of them have any server-side rendering going on.

When I run the "fetch and render as Google" tool on Search Console, the React one displays as expected (and I can even verify that it's getting indexed by running searches against it).

When I do the same against the Angular one, I can see that Google is not capturing much of the information on the page:

wah woh

What factor is at play here for one to render properly, and not the other? What can I do to ensure that a site made with a single-page framework is crawled correctly by Google?

  • 1
    For the second site, the validator can't get through the whole page and that could be what's tripping up Google, too.
    – Rob
    Commented Apr 11, 2016 at 20:58
  • @Rob looking at that makes me wonder if Google gets tripped up on custom HTML elements? A difference between React and Angular is that React outputs everything in normal elements, whereas Angular will output custom ones.
    – ccnokes
    Commented Apr 11, 2016 at 21:48
  • 1
    Have a look at this may help stackoverflow.com/questions/13499040/…
    – Abu Nooh
    Commented Apr 11, 2016 at 22:19

1 Answer 1


I'm gonna answer this in terms of general frameworks because generally questions too specific on the details of one website are closed here.

For any engine to be able to successfully render data, you want to make it as basic and as easy to understand as possible. In the early days, no search engine was able to render Javascript code. This means that if a website was done entirely in javascript, then clients without javascript enabled will see nothing.

What you want to do to ensure almost any tool can render (at least the text of) your page is to ensure its accessible via basic HTML.

I would suggest testing your pages (regardless of framework used to generate the code) with as many browsers as possible including the old-fashioned lynx browser.

While I do understand google processes some Javascript, I'm sure its limited. For this reason, if you must use Javascript to render your pages, use the level of scripting that an ancient browser (like Internet explorer 7 or under) can support.

  • Google can render a whole react app, including front end routing with react router without any real limitation. Tested in production accross several websites.
    – Mijamo
    Commented Apr 12, 2016 at 8:18
  • Thats the thing. you gotta test everything to make sure it works. Commented Apr 12, 2016 at 13:13
  • @Mijamo Did you do anything to test the crawl-ability of your site before you went into production? In the future, I'd like to know if my site's crawl-able before it's go-live date...
    – ccnokes
    Commented Apr 12, 2016 at 15:17
  • I tried "fetch as google" with the test version (which was on a subdomain) with noindex metatags on all the pages to ensure that Google does not index them in any way.
    – Mijamo
    Commented Apr 13, 2016 at 7:01

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.