6

My site is in AngularJS, so I recently created HTML snapshots of all my content, added the escaped fragment tag to the head of all my pages (meta name="fragment" content="!"), and then tried to test to see if the new setup was working in Webmaster Tools. When I look in the source I see the escaped fragment (however, it's inverted) (meta content="!" name="fragment"). I'm not sure why that's happening or if that matters...

When I submit a URL to "Fetch as Google," Webmaster Tools returns Fetch Status Not Found. However, if I manually add "?_escaped_fragment_=" to the end of my URL, I get a success status.

So, my question is, does this have something to do with how Webmaster Tools tests URLs or have I set up fragment escaping incorrectly?

Bailey Smith
  • 2,853
  • 4
  • 27
  • 39

2 Answers2

9

Apparently "Fetch as Google" does not fetch the same way that Google does. When using "Fetch as Google" the page isn't checked for the meta tag. However, obviously, Google does check the page for the meta tag when crawling.

Bailey Smith
  • 2,853
  • 4
  • 27
  • 39
  • Did you manage to test this somehow? I'm facing the same issue. – adamors Jun 23 '14 at 17:07
  • The best workaround I could come up with was adding `?_escaped_fragment_=` to the end of my url, and then submitting it to "Fetch as Google." (e.g. `www.thisthing.com/items/424?_escaped_fragment_=`) – Bailey Smith Jun 24 '14 at 21:33
  • 1
    Yeah, that's what I'm doing as well. Thanks anyways, this really sucks. – adamors Jun 25 '14 at 08:53
  • It seems to only work manually, perhaps you guys want to have a look at my related question, http://stackoverflow.com/questions/24446065/google-bot-crawling-on-angularjs-site-with-html5-mode-routes – Iraklis Alexopoulos Jun 27 '14 at 08:51
  • 1
    This is very disappointing. My company is worried about the risk to our SEO if we launch without being able to test this feature through Google's WMT. – JaredMcAteer Mar 13 '15 at 21:46
0

add a client side "easter egg" keypress that takes the browser's current location and generate the '_escaped_fragment_' form, making sure to escape as needed, and then tell the browser to load that location.

Then to test all you have to do is press your magic key-press and the browser will then redirect to your escaped fragment rendered page.

You can then copy/paste this newly created url into sitemarkup testers, etc.

Michael Joyner
  • 96
  • 1
  • 5