angular: currency pipe breaks rendering of Googlebot's "Fetch as Google" in Google Search Console

I’m submitting a … (check one with “x”)

[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

When using the “Fetch as Google” tool within the Google Search Console, specifically the Fetch and Render option, the page’s dynamically loaded asynchronous content does not show up while the currency pipe is being used within the page. This is how Google renders the page with the pipe: screen shot 2017-03-22 at 5 18 23 pm

Expected behavior

The page should load fine and be rendered by google while the currency pipe is being used. This is how Google renders the page with the pipe commented out: screen shot 2017-03-22 at 5 18 45 pm

Minimal reproduction of the problem with instructions

Use the currency pipe inside of a page that displays dynamically loaded content via a RESTful API, then use the Fetch as Google tool on Google’s Search Console. Select the “Fetch and Render” option. Once the fetch and render is complete, view the results. The page will not show any of the dynamically loaded content.

What is the motivation / use case for changing the behavior?

SEO optimization

Please tell us about your environment:

{npm: ‘4.0.5’, ares: ‘1.10.1-DEV’, cldr: ‘30.0.3’, http_parser: ‘2.7.0’, icu: ‘58.2’, modules: ‘51’, node: ‘7.4.0’, openssl: ‘1.0.2j’, tz: ‘2016j’, unicode: ‘9.0’, uv: ‘1.10.1’, v8: ‘5.4.500.45’, zlib: ‘1.2.8’ }

  • Angular version: 2.0.X

angular-cli: 1.0.0-beta.28.3 node: 7.4.0 os: linux x64 @angular/common: 2.4.7 @angular/compiler: 2.4.7 @angular/core: 2.4.7 @angular/forms: 2.4.7 @angular/http: 2.4.7 @angular/material: 2.0.0-beta.1 @angular/platform-browser: 2.4.7 @angular/platform-browser-dynamic: 2.4.7 @angular/router: 3.4.7 @angular/compiler-cli: 2.4.7

  • Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Chrome

  • Language: [all | TypeScript X.X | ES6/7 | ES5] TypeScript
  • Node (for AoT issues): node --version =
    v7.4.0

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Reactions: 1
  • Comments: 15 (8 by maintainers)

Most upvoted comments

it was my initial idea, but shouldn’t it throw an error in this case?

@DzmitryShylovich since this is server-side rendering I wouldn’t assume anything 😃