URLs on Google doc change

생성일 비교 결과 만료 없음
109 삭제
134 행
106 추가
127 행
URL structure best practices for Google
URL structure best practices for Google Search

bookmark_border
To make sure Google Search can crawl your site effectively, use a crawlable URL structure that meets the following requirements. If your URLs don't meet the following criteria, Google Search will likely crawl your site inefficiently — including but not limited to extremely high crawl rates, or not at all.

Requirements for a crawlable URL structure
Follow IETF STD 66
Google supports URLs as defined by RFC 3986. Characters defined by the standard as reserved must be percent encoded. Unreserved ASCII characters may be left in the non-encoded form. Additionally, characters in the non-ASCII range should be UTF-8 encoded.
Google Search supports URLs as defined by IETF STD 66. Characters defined by the standard as reserved must be percent encoded.

Don't use URL fragments to change content
Don't use fragments to change the content of a page, as Google Search generally doesn't support URL fragments. Here's an example of a URL fragment:

https://example.com/#/potatoes
If you're using JavaScript to change content, use the History API instead.

Use a common encoding for URL parameters
When specifying URL parameters, use the following common encoding: an equal sign (=) to separate key-value pairs and add additional parameters with an ampersand (&). To list multiple values for the same key within a key-value pair, you can use any character that doesn't conflict with IETF STD 66, such as a comma (,).

Recommended Not recommended
Using an equal sign (=) to separate key-value pairs and an ampersand (&) to add additional parameters:
https://example.com/category?category=dresses&sort=low-to-high&sid=789
Using a colon (:) to separate key-value pairs and brackets ([ ]) to add additional parameters:
https://example.com/category?[category:dresses][sort:price-low-to-high][sid:789]
Using a comma (,) to list multiple values for the same key, an equal sign (=) to separate key-value pairs, and an ampersand (&) to add additional parameters:
https://example.com/category?category=dresses&color=purple,pink,salmon&sort=low-to-high&sid=789
Using a single comma (,) to separate key-value pairs and double commas (,,) to add additional parameters:
https://example.com/category?category,dresses,,sort,lowtohigh,,sid,789
Make it easy to understand your URL structure
To help Google Search (and your users) better understand your site, we recommend creating a simple URL structure, applying the following best practices when possible.


Consider organizing your content so that URLs are constructed logically and in a manner that is most intelligible to humans. For information on structuring your site as a whole, check out this section of the SEO Starter Guide.
Best practices
Use descriptive URLs
When possible, use readable words rather than long ID numbers in your URLs.
When possible, use readable words rather than long ID numbers in your URLs.


Recommended: Simple, descriptive words in the URL:
Recommended (simple, descriptive words) Not recommended (unreadable, long ID numbers)


https://en.wikipedia.org/wiki/Aviation
https://example.com/wiki/Aviation
https://example.com/index.php?topic=42&area=3a5ebc944f41daa6f849f730f1
Use your audience's language
Recommended: Use words in your audience's language in the URL (and, if applicable, transliterated words). For example, if your audience is searching in German, use German words in the URL:
Use words in your audience's language in the URL (and, if applicable, transliterated words). For example, if your audience is searching in German, use German words in the URL:




https://example.com/lebensmittel/pfefferminz
https://example.com/lebensmittel/pfefferminz
Recommended: Use UTF-8 encoding as necessary. For example, the following example uses UTF-8 encoding for Arabic characters in the URL:
Or if your audience is searching in Japanese, use Japanese words in the URL:




https://example.com/ペパーミント
Use UTF-8 encoding as necessary
When linking to pages on your site, use UTF-8 encoding in your links's href attributes as necessary. Unreserved ASCII characters may be left in the non-encoded form. Additionally, characters in the non-ASCII range should be UTF-8 encoded. For example:

Recommended (UTF-8 encoding) Not recommended (non-ASCII characters)
https://example.com/%D9%86%D8%B9%D9%86%D8%A7%D8%B9/%D8%A8%D9%82%D8%A7%D9%84%D8%A9
https://example.com/%D9%86%D8%B9%D9%86%D8%A7%D8%B9/%D8%A8%D9%82%D8%A7%D9%84%D8%A9
The following example uses UTF-8 encoding for Chinese characters in the URL:
https://example.com/نعناع


https://example.com/%E6%9D%82%E8%B4%A7/%E8%96%84%E8%8D%B7
https://example.com/%E6%9D%82%E8%B4%A7/%E8%96%84%E8%8D%B7
The following example uses UTF-8 encoding for the umlaut in the URL:
https://example.com/杂货/薄荷


https://example.com/gem%C3%BCse
https://example.com/gem%C3%BCse
The following example uses UTF-8 encoding for emojis in the URL:
https://example.com/gemüse


https://example.com/%F0%9F%A6%99%E2%9C%A8
https://example.com/%F0%9F%A6%99%E2%9C%A8
Not recommended: Using non-ASCII characters in the URL:


https://example.com/نعناع

https://example.com/杂货/薄荷

https://example.com/gemüse

https://example.com/🦙✨
https://example.com/🦙✨
Not recommended: Unreadable, long ID numbers in the URL:
Use hyphens to separate words


https://example.com/index.php?id_sezione=360&sid=3a5ebc944f41daa6f849f730f1
Don't use fragments to change the content of a page, as Google generally doesn't support URL fragments. If you're using JavaScript to change content, use the History API instead.

Not recommended: URL fragments:


https://example.com/#/potatoes
If your site is multi-regional, consider using a URL structure that makes it easy to geotarget your site. For more examples of how you can structure your URLs, refer to using locale-specific URLs.

Recommended: Country-specific domain:


https://example.de
Recommended: Country-specific subdirectory with gTLD:


https://example.com/de/
Consider using hyphens to separate words in your URLs, as it helps users and search engines identify concepts in the URL more easily. We recommend that you use hyphens (-) instead of underscores (_) in your URLs.
We recommend separating words in your URLs, when possible. Specifically, we recommend using hyphens (-) instead of underscores (_) to separate words in your URLs, as it helps users and search engines better identify concepts in the URL. For historical reasons, we don't recommend using underscores, as this style is already commonly used for denoting concepts that should be kept together, for example, by various programming languages to name functions (such as format_date).

Recommended: Hyphens (-):