After setup, be sure to do this: How to verify directly through the page source

In the settings screen, it clearly indicates that the information has been saved, but sometimes the search results display titles that seem incorrect. In such cases, the first place to check is not the administrator’s screen, but the web pages that are publicly accessible to visitors.

The only question is: how can I know if the SEO settings I saved have actually been applied to the actual page? The answer lies in directly checking the source code of the public page.

SEO settings are completed within the public HTML.

WordPress SEO settings do not simply end with the values being saved in the administrator screen. They become meaningful only when the title, description, and search-related rules are actually output in the HTML that is delivered to visitors.

HTML is the basic document that forms a web page. Google describes the title element within this document, as well as the meta name description element that contains a description, and the robots meta tag, as information that can be used for searching and crawling.

The screen and the sauce may vary.

The appearance on the browser screen and the HTML initially sent by the server may differ. According to the Chrome documentation, the browser reads the HTML sent by the server to create the screen structure, and then JavaScript can modify that structure.

Therefore, when verifying whether the initial output is correct, it is safer to use the “View Page Source” option rather than the “Elements” feature in the developer tools.

Even if the search results are different, it does not necessarily mean that the settings have failed.

The reason people are curious about this is simple: the title and description they set do not appear exactly as they are in the search results or sharing screens.

Google does not fix the search result title based on just one title. It can automatically generate titles by referencing the main title of the page, the text used for display purposes, og:title, the body text, and the text used in external links.

The same applies to the description. While a meta description can be used as a short sentence in search results, Google may choose to display a different sentence from the main body of the page.

The search results are not a copy of the settings.

Sometimes, the revised title or description may not immediately appear in the search results. Google states that it may take several days to several weeks for the changes to be reflected.

Therefore, you should not conclude that the settings were not saved simply because the search results are different.

Immediately after setup, please check the following four items.

In short, you should trust the source code of the public page more than the completion indicator in the settings screen. Only then should you separately verify whether Google has actually read and indexed it.

Open the page you want to check using its public address. In the browser, select “View Page Source,” and then find the following items within the source code.

  • title: Page title to be referenced in search results.
  • description: A description summarizing the content of the page.
  • robots: Rules related to search engine visibility.
  • canonical: This is the canonical URL for this page.

If you have found four matches, do not stop at simply confirming their existence; you must also compare their values. Verify that the configured phrase is correct, and that the actual page address and the canonical URL are correct.

If you see “noindex” on a page you are trying to publish, you should stop first. Google describes “noindex” as a rule that prevents a page from being displayed in search results, so if you see this value on a page you are publishing, you need to correct the settings.

Conversely, if a page should not be included in search results, verify that the `noindex` directive is being output as intended. This involves checking whether the content selected in the administrator interface matches the publicly visible HTML.

Points and limitations encountered during direct verification.

In reality, even after opening the source code, it may take a long time to find what you are looking for. This can happen when the title or description appears multiple times, when the desired phrase is not visible, or when the canonical URL points to a different address.

It is a common mistake to judge solely based on the Elements of the developer tools. The Elements may show the state of the page after JavaScript execution, which can lead to displaying results different from the original document sent by the server.

It is not enough for all tags to be displayed. If the same type of title or description overlaps, it is difficult to determine visually which value will be used, and it is also necessary to check whether the template or plugin has added different values.

Direct verification is strong for confirming output, but it does not automatically identify the cause.

A canonical URL should not be viewed as a single entity. Google allows the use of canonical URLs when specifying a preferred URL, and recommends maintaining consistency in internal site links, sitemaps, and canonical URLs.

The `robots.txt` file and the robots meta tag should not be considered the same thing. Google explains that the `robots.txt` file is not a mechanism for removing pages from the index.

Following up on the SOHO SEO audit.

Even after verifying the actual output from open sources, it may still be necessary to continuously manage the technical and structural elements of a post and website. SOHO SEO is a plugin for WordPress that checks and manages these elements, allowing users to view the SEO score of a published article, as well as the featured image, title, author, and structured data, all within the article editing screen.

The plugin automatically outputs Article structured data. It also allows you to enable or disable standard XML sitemaps and news sitemaps. You can also specify the scope of the noindex setting for archive types such as date, author, tags, and search results. The robots.txt file and the sitemaps provided by this plugin should be checked regularly, and the plugin will notify you if any issues are detected.

Separate the source verification process from the Google verification process.

Verifying the page source is the step to determine whether the settings have been rendered as actual HTML. Whether the page is indexed and whether the search results are reflected need to be checked separately afterward.

The following steps should be taken:

  1. Open the public page.
  2. Find the title, description, robots, and canonical elements in the page source code.
  3. Compare the specified phrase with the actual output value.
  4. Check for the existence of `noindex` and other canonical URLs.
  5. If you use structured data, you can verify its validity using the Google Rich Results Test.
  6. Whether a page is indexed and the status of its indexing can be checked using the URL inspection tool in Google Search Console.

The “Leech” result test is a tool that verifies whether structured data conforms to the grammar. Passing the test does not necessarily mean that a special indicator will appear in the search results.

The URL inspection tool is used to check how a specific address appears in the Google index, and to request a real-time index test and a re-crawling request.

If you have just saved a setting, first check the four tags.

If a “noindex” tag is found on a public page, or if the canonical tag points to a different address, you should check for conflicts between settings and plugins, as well as template output, before waiting for search results.

When examining situations where the `noindex` and `canonical` settings are inconsistent, it is first necessary to define the scope of what can be managed. SOHO SEO’s “noindex management” feature allows you to specify the scope of pages to which the `noindex` directive should be applied, including archive types such as date, author, tags, and search results.

We do not provide the option to set the “noindex” setting for individual posts and pages. Therefore, you should not assume that this feature can resolve “noindex” issues for all public pages. If the “canonical” setting points to a different address, you must check the public HTML and the output from templates and plugins separately.

If all the tags are correct but the search results are different, do not immediately conclude that it is a failure. This is because Google can recreate the title and description, and it may take time for the changes to be reflected.

Frequently Asked Questions.

Q. How do I open the Page Source, and what should I look for on my website?

A. To do this, open the public page and use the browser’s “View Page Source” feature. Instead of using the “Elements” section of the developer tools, check the `title`, `description`, `robots`, and `canonical` tags in the HTML that the server initially sent.

Q. What should be done if a public page shows “noindex” or if the canonical URL points to a different address?

A. If you want a page to appear in search results, you should first check the SEO settings, plugin conflicts, and template output. The “noindex” directive prevents a page from being displayed in search results, and if the “canonical” URL points to a different address, you should also verify the canonical URL setting.

Q. Can this problem be easily solved using a tool? What kind of tool should be used?

A. To check if the content is being rendered in HTML, view the page source. To verify structured data, use the Google Rich Results Test. You can check the indexing status and how Google actually perceives the content separately using the URL inspection tool in Search Console.

Q. Where is the “noindex” setting for the archive types page managed?

A. In SOHO SEO’s “noindex management” feature, you can specify the scope of which archive types pages (such as those containing dates, authors, tags, or search results) will have the “noindex” directive applied.

The setting applies to archive type pages, not individual posts or pages. After applying the setting, it is also necessary to check the robots meta output in the source code of public pages.

WordPress-related links

https://sohoseo.luxdigest.com
https://store.luxdigest.com
https://wpcm.luxdigest.com