Debug Rendering Problems

If you suspect that your content isn't processed or rendered correctly on Google Search, please review our debugging tips, and try one of the following methods to test and debug the problem:

  1. Use the Fetch and Render as Google tool in Search Console to test how Google crawls and renders a URL on your site. You can request the "fetch and render" for a specific URL, inspect the HTTP response headers, and view the visual preview of the page, as seen by Google Search.
  2. Audit JavaScript execution errors by logging the errors. Here's an example snippet that shows how to log JavaScript errors logged to the global onerror handler.
window.addEventListener('error', function(e) {
    var errorText = [
        'URL: ' + e.filename,
        'Line: ' + e.lineno + ', Column: ' + e.colno,
        'Stack: ' + (e.error && e.error.stack || '(no stack trace)')

    // Example: log errors as visual output into the host page.
    // Note: you probably don’t want to show such errors to users, or
    //       have the errors get indexed by Googlebot; however, it may
    //       be a useful feature while actively debugging the page.
    var DOM_ID = 'rendering-debug-pre';
    if (!document.getElementById(DOM_ID)) {
        var log = document.createElement('pre'); = DOM_ID; = 'pre-wrap';
        log.textContent = errorText;
        if (!document.body) document.body = document.createElement('body');
        document.body.insertBefore(log, document.body.firstChild);
    } else {
        document.getElementById(DOM_ID).textContent += '\n\n' + errorText;

    // Example: log the error to remote service.
    // Note: you can log errors to a remote service, to understand
    //       and monitor the types of errors encountered by regular users,
    //       Googlebot, and other crawlers.
    var client = new XMLHttpRequest();'POST', '');
    client.setRequestHeader('Content-Type', 'text/plain;charset=UTF-8');


If you need additional help, visit the Webmaster Help Forum.