{"id":25629,"date":"2026-09-05T02:46:51","date_gmt":"2026-09-04T23:46:51","guid":{"rendered":"https:\/\/alienroad.com\/google-bilgi-bankasi\/debugging-your-pages\/"},"modified":"2026-09-06T00:51:51","modified_gmt":"2026-09-05T21:51:51","slug":"debugging-your-pages","status":"publish","type":"ar_kb","link":"https:\/\/alienroad.com\/google-bilgi-bankasi\/debugging-your-pages\/","title":{"rendered":"Debugging your pages"},"content":{"rendered":"<div class=\"video-wrapper\" style=\"margin-top: 20px;\">\n<\/div>\n<h2 id=\"general-tips\" tabindex=\"-1\">\n  General tips<br \/>\n<\/h2>\n<p>\n  Remember that Google does not crawl your page immediately after you publish a fix. Therefore<br \/>\n  <a href=\"https:\/\/search.google.com\/search-console\" class=\"external-link\">Search Console<\/a> (and Google Search) can<br \/>\n  continue to show an error for a page that you have fixed<br \/>\n  until the page is crawled again. You can sometimes request an expedited crawl, for example<br \/>\n  using the <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9012289\" class=\"external-link\">URL Inspection<\/a><br \/>\n  tool, but in most cases it takes a few days to notice changes in your pages.\n<\/p>\n<h2 id=\"useful-testing-tools\" tabindex=\"-1\">\n  Useful testing tools<br \/>\n<\/h2>\n<p>\n  Here are some useful tools to help you debug your pages.\n<\/p>\n<h3 id=\"verified-site-owner-tools\" tabindex=\"-1\">\n  Verified site owner tools<br \/>\n<\/h3>\n<p>\n  The following tools and reports require you to be a<br \/>\n  <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9008080\" class=\"external-link\">verified site user<\/a><br \/>\n  for the page in order to use this tool on that page or site. This is because Search Console<br \/>\n  provides confidential site data that only a verified site user should have access to.\n<\/p>\n<ul>\n<li>\n    <a href=\"https:\/\/search.google.com\/search-console\" class=\"external-link\">Search Console<\/a> &#8211;<br \/>\n    Sign up for Search Console and <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9008080\" class=\"external-link\">verify ownership of a site<\/a><br \/>\n    to get access to useful site monitoring and testing tools,<br \/>\n    such as those listed below.\n  <\/li>\n<li>\n    <a href=\"https:\/\/support.google.com\/webmasters\/answer\/7552505\" class=\"external-link\">Rich result status reports<\/a><br \/>\n      &#8211; Learn which rich results Google could or couldn&#8217;t read from your site, get<br \/>\n    troubleshooting information for rich result errors, and request a recrawl after you have<br \/>\n    fixed any problems. You cannot test an arbitrary URL using this tool.\n  <\/li>\n<li>\n    <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9012289\" class=\"external-link\">URL Inspection tool<\/a><br \/>\n    &#8211; Learn how your page appears in the Google index, run an index test on a live URL, and<br \/>\n    see how Google renders your page, and submit a URL for indexing.\n  <\/li>\n<li>\n    <a href=\"https:\/\/support.google.com\/webmasters\/answer\/6062598\" class=\"external-link\">Robots.txt report<\/a><br \/>\n    &#8211; Check whether Google can process your robots.txt files. You an also request a recrawl of<br \/>\n    a robots.txt file for emergency situations.\n  <\/li>\n<li>\n    <a href=\"https:\/\/search.google.com\/search-console\/amp\" class=\"external-link\">AMP status report<\/a> &#8211; See AMP page<br \/>\n    errors for your entire site detected by Google. Errors are detected during the regular<br \/>\n    crawl; you cannot test an arbitrary URL.\n  <\/li>\n<\/ul>\n<h3 id=\"anonymous-tools\" tabindex=\"-1\">\n  Anonymous tools<br \/>\n<\/h3>\n<p>\n  These tools can be used on any URL without needing Search Console permissions on the website.<br \/>\n  Some tools also allow code snippets pasted into the tool itself.\n<\/p>\n<p>\n  If your URL is behind a firewall, or is hosted on a local computer, you can use a tunnelling<br \/>\n  solution to expose your page to the testing tool. <a href=\"#testing-firewalled-pages\">Learn how to test locally-hosted or firewalled pages.<\/a>\n<\/p>\n<ul>\n<li>\n    <a href=\"https:\/\/search.google.com\/test\/amp\" class=\"external-link\">AMP Test Tool<\/a><br \/>\n    &#8211; Test the validity of a specific AMP URL in real time.\n  <\/li>\n<li>\n    <a href=\"https:\/\/search.google.com\/test\/rich-results\" class=\"external-link\">Rich Results Test<\/a> &#8211; Test<br \/>\n    the validity of a structured data block in real time. The<br \/>\n    code can either be pasted into the tool, or hosted on a live page.\n  <\/li>\n<\/ul>\n<h3 id=\"more-tools\" tabindex=\"-1\">\n  More tools<br \/>\n<\/h3>\n<p>\n  See <a href=\"https:\/\/developers.google.com\/search\/help\">our help page<\/a> for more resources and office hours information.\n<\/p>\n<h2 id=\"testing-firewalled-pages\" tabindex=\"-1\">\n  Testing locally-hosted or firewalled pages<br \/>\n<\/h2>\n<p>\n  Google provides several testing tools to test a single live web page. For example, the<br \/>\n  <a href=\"https:\/\/search.google.com\/test\/amp\" class=\"external-link\">AMP Test Tool<\/a> and the<br \/>\n  <a href=\"https:\/\/search.google.com\/test\/rich-results\" class=\"external-link\">Rich Results Test<\/a>.<br \/>\n  However, if your page is running on your local machine without a public<br \/>\n  URL, or if it is hosted behind a firewall, you can still test the page by exposing a tunnel to<br \/>\n  your page for the testing tool.<br \/>\n  This can be useful if you want to test a page before making it publicly available on the web,<br \/>\n  or even as another step in your release process.<\/p>\n<p>\n  To test a local or firewalled page, use a tunneling solution such as <code>ngrok<\/code>. These<br \/>\n  tools provide a public URL that connects to a non-public page on your local host or firewalled<br \/>\n  server.\n<\/p>\n<p>\n  The following example first starts up python&#8217;s<br \/>\n  <a href=\"https:\/\/docs.python.org\/2\/library\/simplehttpserver.html\" class=\"external-link\"><code>SimpleHTTPServer<\/code><\/a><br \/>\n  to host a page on the local computer, then uses<br \/>\n  <a href=\"https:\/\/ngrok.com\/\" class=\"external-link\">ngrok<\/a> to expose that page on a<br \/>\n  publicly-accessible URL:\n<\/p>\n<p><strong>Step 1<\/strong><\/p>\n<p>\n  Start up a local HTTP server to host your page on a given port. For our example we chose port<br \/>\n  <code>5326<\/code>.\n<\/p>\n<p>\n  <code>SimpleHTTPServer<\/code> maps the current directory as the site root.\n<\/p>\n<div><\/div>\n<p>\n  <strong>Step 2<\/strong>\n<\/p>\n<p>\n  On another terminal, start up your local <code>ngrok<\/code> app, listening to port<br \/>\n  <code>5326<\/code>, which we opened in step 1.\n<\/p>\n<div><\/div>\n<p>\n  <strong>Step 3<\/strong>\n<\/p>\n<p>\n  Pass your exposed ngrok URL to the test tool of your choice.\n<\/p>\n<p>\n  The root URL in our example is <code>http:\/\/ad0a5735.ngrok.io<\/code>, so if our page is saved<br \/>\n  locally at <code>~\/testwebdir\/mypage.html<\/code>, and we started the server above from<br \/>\n  <code>~\/testwebdir\/<\/code>, we could test <code>http:\/\/ad0a5735.ngrok.io\/mypage.html<\/code>.<br \/>\n  In the Rich Results Test, you could paste that URL in directly, or visit<br \/>\n  <code>https:\/\/search.google.com\/test\/rich-results\/result?url=http%3A%2F%2Fad0a5735.ngrok.io%2Fmypage.html<\/code>.\n<\/p>\n<p>\n  Note that different local hosts and tunneling solutions map your pages differently.\n<\/p>\n<p>\n  Also, some tunneling solutions (not ngrok) automatically protect your temporary public URL<br \/>\n  with robots.txt, which will prevent you from running Google tests on them. Google testing<br \/>\n  tools respect robots.txt. Read the documentation for your tunneling solution and web hosting<br \/>\n  software.\n<\/p>\n<h3 id=\"debugging-access-errors\" tabindex=\"-1\">\n  Debugging access errors<\/h3>\n<p>\n  If you get an access error using a Google testing tool:\n<\/p>\n<ul>\n<li>Check that your page isn&#8217;t protected by robots.txt and doesn&#8217;t require a login.\n  <\/li>\n<li>Try accessing your page from outside your firewall, on another computer, or using Chrome<br \/>\n    in Incognito mode.\n  <\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>If you need to debug a website, there are several useful web debugging tools. Explore this guide for tips on how to debug your website.<\/p>\n","protected":false},"menu_order":5003,"template":"","meta":{"footnotes":""},"ar_kb_kategori":[667],"ar_kb_etiket":[],"class_list":["post-25629","ar_kb","type-ar_kb","status-publish","has-post-thumbnail","hentry","ar_kb_kategori-support"],"_links":{"self":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/25629","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb"}],"about":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/types\/ar_kb"}],"version-history":[{"count":1,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/25629\/revisions"}],"predecessor-version":[{"id":25697,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/25629\/revisions\/25697"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media\/27626"}],"wp:attachment":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media?parent=25629"}],"wp:term":[{"taxonomy":"ar_kb_kategori","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_kategori?post=25629"},{"taxonomy":"ar_kb_etiket","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_etiket?post=25629"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}