where i'm at: i've read google's documentation regarding it's ajax crawling, , i've searched around bit in website , others, i'm quite confused, seems problems address same issue: ajax crawing hashbangs? i've developed app which, among other purposes, let's user search locations worldwide, using ajax searcher quite similar google's, app uses exclusively question mark in ajax, instead of hashbang. due compatibility issues, changing hashbang not option.
not largely confused fact not find else using question mark instead of hashbang, i'm wondering if there documentation regarding my issue: how let google bot crawl ajax content when i'm using question mark instead of hashbang in ajax app.
the ajax crawling schema created explicitly applications , websites using hashbang (#!) in url structure, because fragment part of urls exist on client side; url rewriting in specs, i.e. #! ?_escaped_fragment_= meant solve that.
since of web making use of javascript in way or other, (google) needed better solution, started executing javascript in pages crawled , render every page, normal browser would. quote our blogpost, understanding web pages better:
in order solve problem, decided try understand pages executing javascript. it’s hard @ scale of current web, decided it’s worth it. have been gradually improving how time. in past few months, our indexing system has been rendering substantial number of web pages more average user’s browser javascript turned on.
you can see "see" using fetch google in search console (former webmaster tools); read more feature in our post titled rendering pages fetch google
before else, please try fetch few pages site fetch google. might not have @ all, might work out of box. , news it's not google that's rendering pages!
Comments
Post a Comment