GOOGLE WORRING WORKING THE SITE

When correcting errors on the page of your site on Google, it is important to remember that Google does not scan the page immediately after you have published corrections. Thus, the search console (and Google Search) can continue to show a mistake for the page that you corrected until the page is indexed again. Sometimes you can request accelerated scanning using the URL checking tool, but in most cases it will take several days so that the changes are visible in Google.

General advice on debugging your site in Google

To speed up the correction process, make sure that all corrections are clearly reflected on the page. It is important to regularly check the condition of your pages using available tools and receive page reports in order to understand when your corrections are taken into account in the search results.

Useful tools for debugging pages of your site in Google

There are several useful tools that will help you debug the pages of your site in Google.

Tools for proven site owners

The following tools and reports require you to be a proven user of the site to have access to data on your site provided by the search console. This is necessary so that only trusted owners can see confidential data about the site.

• Search console - register in the search console and confirm ownership of the site to gain access to useful monitoring and testing tools, such as those listed below.
• Reports on the status of advanced results - find out what expanded Google results can or cannot read from your site, get information to eliminate errors and request a second scan after correcting the problems. You cannot test arbitrary URL with this tool.
• URL checking tool - find out how your page is displayed in the Google index, perform an indexation test for a live URL, see how Google renders your page and send the URL to index.
• Report Robots.txt - Check if Google can process your Robots.txt file. You can also request re -scanning the Robots.txt file in emergency cases.
• AMP status report - View AMP Pages on your website that Google discovered during regular scanning. You cannot test the arbitrary URL with this tool.

Anonymous tools for debugging your site pages in Google

These tools can be used on any URL without the need to obtain permits from the search console for use on your site. Some tools also allow you to insert code fragments directly into the tool itself.

If your URL is located behind the firewall or placed on a local computer, you can use the tunneling solution to open your testing page. Find out how to test pages placed locally or behind the firewall.

• AMP test - test the validity of a particular AMP URL in real time.
• Test of advanced results - test the validity of the structure of structured data in real time. The code can be inserted into the tool or placed on a living page.

Additional tools for debugging pages of your site in Google

To obtain additional information and resources, as well as for consultations, you can contact the certificate page, which indicates all the necessary contact details.

How to test the pages of your site in Google locally placed or protected or protected or protected?

Google provides several tools for testing live web pages, such as the AMP testing tool and the test of advanced results. However, if your page works on a local car without a public URL or is located behind a firewall, you can still test the page by opening the tunnel to your testing page.

To test local or fenwall pages, use a tunneling solution, for example, NGROK. These tools provide a public URL that connects your local page or a page on the server behind a fuarwall with a testing tool.

Example: first run the local HTTP server using Python to place a page on a local computer, then use NGROK to open this URL for public access.

An example of debugging the local page of your site in Google using tunneling

Step 1: Run the local server to accommodate your page on the port, for example, port 5326.

python3 -m http.server 5326

Step 2: At another terminal, run NGROK, listening to Port 5326, which you opened at a step 1.

./ngrok http 5326 --request-header-add ngrok-skip-browser-warning:1

Step 3: Pass the open URL NGROK to the selected testing tool to check the page. For example, if your URL looks like http://ad0a5735.ngrok.io, you can test it through Test of advanced results.

Surveying errors of access to the pages of your site in Google

If, when using Google testing tools, access errors occur:

• Check if your page is protected using robots.txt and does it require entering the system.
• Try to access the page from a computer outside your firewall, or use incognito-mode in Chrome.

For additional assistance, you can contact the SEO.computer SEO company for any issue on email info@seo.computer Or WhatsApp +79202044461.

ID 193