Leave a request
In order for Google Search to effectively index your site, use the URL structure available for bypass, which meets the following requirements. If your URLs do not meet these criteria, Google Search can ineffectively go around your site, which can lead to high loads on the server or complete impossibility of bypass.
Google Search supports the URL, determined by the IETF STD 66 standard. The characters that are considered reserved in this standard should be encoded using interest.
Do not use URL fragments to change the page content, since Google Search, as a rule, does not support URL fragments. Here is an example of a fragment of the URL:
HTTPS: // Example
If you use JavaScript to change content, use the History API instead.
When specifying the URL parameters, use the following encoding format: equal sign (=) for separating the pair "key-value" and ampersand (&) to add additional parameters. To specify several values for one key in the parameter, you can use any symbols that do not conflict with IETF STD 66, such as a comma (,).
Recommended:
HTTPS: // Example.Kom.kategoria? Categories = Dresses & Variety = Sweeter-High & Sid = 789
Not recommended:
HTTPS: // Example.Kom.kategoria? Yukategory :dresses ] [sort :price -low-to-high] [SID: 789]
In order for Google Search (and your users) to understand your site better, we recommend using the simple URL structure and apply the following best practices when possible.
Consider the possibility of organizing content so that the URL is built logically and are most understandable for people. To get information about the structure of your site, read the Seo Starter Guide section.
When possible, use readable words instead of long identifiers in the URL.
Recommended: HTTPS: // Example.Kom/viki/Avaition
Not recommended: HTTPS: // Example.Kom/Index.PHP? Topik = 42 & Area = for5evk9441DAABF849F730F1
Use the words in the language of your audience in the URL (and, if necessary, translicted words). For example, if your audience is looking for in German, use German words in the URL:
HTTPS: // Example.K.M.Komitel/pfefferins
Or if your audience is looking for in Japanese, use Japanese words in the URL:
https://example.com/ ペパーミント
When links to the pages of your site, use the UTF-8 encoding in HREF attributes as necessary. Not reserved ASCII characters can be left in the original form, and the symbols from the non-USCII range should be encoded using UTF-8. For example:
Recommended: HTTPS: // Example.com/%86%D8%B9%86%86%D8%A7%D8%D
Not recommended: https://example.com/ ursimes.
It is recommended to separate words in the URL when possible. Specifically, we recommend using hyphens (-) instead of emphasizing (_) to divide words into URL, as this helps users and search engines better understand the concepts reflected in the URL.
Recommended: HTTPS: // Example.K.Mommer-prlothing/filtre? Color-profile = Dark-Gray
Not recommended: HTTPS: // Example.Kom/summer_Tslothing/filtre? Color_profile = Dark_ Grey
When possible, reduce the URL by removing unnecessary parameters (that is, those that do not change content).
Like any other HTTP client, following the IETF STD 66 standard, URL processing in Google Search is sensitive to the register (for example, Google perceives /Apple and /Apple as different URLs with different content). If your server processes the text in the URL in the upper and lower register the same way, convert the entire text into one register to facilitate Google understanding that these URLs indicate the same page.
If your site is multilingual, think about creating a URL structure that facilitates the geographical targeting of your site. For examples, how to structure urls, read the recommendations for the use of localized URLs.
It is recommended (using a domain specific to the country): HTTPS: // Example
Recommended (using a subcatalog for a country with GTLD): HTTPS: // Example.Kom/de/
Too complicated URLs, especially containing several parameters, can create problems for search engines, creating an extra number of URLs indicating identical or similar content on your site. This can lead to the fact that Googlebot will consume too many passes bands or Google Search will not be able to completely index all the content of your site.
Too many URLs can be caused by several problems, such as:
Many sites provide various representations of the same set of elements or search results, often allowing the user to filter this set using certain criteria (for example: show me hotels on the beach). When filters can be combined additively (for example: hotels on the beach and with a fitness center), the number of URLs on the site increases sharply.
Unfulfilled parameters in the URL can cause a large number of URLs, for example:
Think about Googlebot access to these problematic URLs using Robots.txt.
A dynamically generated calendar can create links to future and past dates without restrictions on the dates of the beginning and end. For example:
HTTPS: // Example.Kom.kaledar.PHP? D = 13 & M = 8 & and = 2011
If you notice that Google Search processes these problematic url, we recommend the following:
If you have questions or problems with SEO, contact the "seo.computer" team on any question. We will help you improve the URL structure for your Google site.
Contact information: email: info@seo.computer, WhatsApp: +79202044461
ID 14
