Problems of site indexing: consideration of technical aspects of domains and subdomains
At a recent Google Office Hours, John Mueller answered questions about website indexing issues. The discussion revealed a technical aspect of domains and subdomains that may not be obvious to many. Such technical nuances can cause the impression that the site has problems with indexing.
"I created a new site on Core MVC and moved it to HTTPS and I'm having trouble indexing the new pages."
Mueller tested the site and found that neither the MVC framework nor HTTPS were the cause of the indexing issues noted. He found out that the site was indexed without the www subdomain, so when searching for the www version of the site, there weren't many results. However, if you search for a domain without www, for example, site:domain.com, the site is indexed.
- 📌 The version of the site with www is actually a subdomain of the version of the site without www.
- 📌 Indexing may differ for domain and subdomain.
- 📌 HTTPS and the framework used usually do not cause problems with indexing.
Can HTTPS affect indexing?
Usually, HTTPS does not cause problems with indexing.
Can the framework affect indexing?
As a rule, the framework used does not affect indexing.
Can indexing be different for a domain and a subdomain?
Yes, indexing can be different for a domain and a subdomain.
Статтю згенеровано з використанням ШІ на основі зазначеного матеріалу, відредаговано та перевірено автором вручну для точності та корисності.
https://www.searchenginejournal.com/google-on-how-subdomain-caused-perception-of-indexing-issue/504673/