On Google Search Result Pages (SERP), a webpage’s visibility is determined by over 200 algorithmic indicators.
Data shows: an optimized meta description can increase search result Click-Through Rate (CTR) by 15%-30%—users often decide whether to click within 0.5 seconds based on the title and description.
If the viewport (mobile adaptation tag) is set incorrectly, mobile rankings can drop directly by 15%-20%, while global mobile search share has exceeded 60% (StatCounter 2024).
This article focuses on the 14 most critical meta tags in Google SEO, breaking down “what happens if set incorrectly” and “how to verify correct implementation” one by one, supported by real cases and official Google guidelines to help you avoid 90% of ineffective operations.
Core Basic SEO Meta Tags
On Google Search Result Pages (SERP), the average time a user takes to decide whether to click a link is only 0.8 seconds (Google User Behavior Study, 2023).
In these 0.8 seconds, titles (<title>) and descriptions (<meta name=”description”>) account for 70% of the click decision.
Meta tags also directly affect Google’s crawling and indexing. For example, incorrect use of the noindex directive in <meta name=”robots”> can lead to a page never being indexed (even if the content is cited by other pages).
<title>
Although <title> is not technically a <meta> tag, it is the top priority signal Google uses to evaluate page topics (Google Official Guidelines, 2024).
The first line of search results users see is the title, which directly determines “whether to click.”
Key Configuration Rules (Based on Ahrefs statistics of 100,000 high-click pages):
Length: 50-60 characters. Over 60 characters will be truncated (mobile is even shorter, around 50 characters).
- Negative Case: An education website homepage title reads “2024 Latest Primary to High School Full Subject Learning Materials Download, covering Math Chinese English Physics Chemistry, Free to Collect with No Strings Attached”—character count 98, mobile displays as “2024 Latest Primary to High School Full Subject Learning Materials Download, cov…”—users cannot see the core selling point “Free to Collect.”
- Positive Case: A parenting blog article title “2-Year-Old Baby Food Supplement Schedule (with 10 Easy Recipes)”—character count 42, displays fully, includes specific age and “recipes” keywords, CTR is 22% higher than similar pages.
Keyword Position: Place core keywords in the first half. Users focus more on the beginning of the title (Eye-tracking studies show 70% of user gaze is concentrated on the first 30 characters).
- Incorrect Example: “[Latest] 2024 Beijing Renovation Company Rankings, professionally providing villa, apartment, and old house renovation design services”—the keyword “Beijing Renovation Company” is in the 6th position.
- Correct Example: “Beijing Renovation Company 2024 Latest Rankings: Villa/Apartment/Old House Renovation Design Service Recommendations”—keywords front-loaded, CTR increased by 18%.
Uniqueness: Each page title must be unique. Google will lower the ranking of pages with duplicate titles (Moz data from crawling 500 sites shows that pages with duplicate titles rank on average 1.2 positions lower than those with unique titles).
The core of <title> is “letting users know at a glance what problem the page can solve,” rather than keyword stuffing.
<meta name=”description”>
The description tag is the “persuasive text” secondary only to the title in search results. A high-quality description can increase CTR by 15%-30% (Moz 2023 test data on 1000 keywords).
3 Key Points for Writing Descriptions:
Length Control: 150-160 characters. Over 160 characters will be truncated (Google defaults to truncation, with some devices showing even less).
- Negative Case: A travel website page description reads “Providing global popular travel destination guides, including Southeast Asian islands, European old towns, domestic ancient towns, as well as hotel bookings, flight comparisons, and local food recommendations, solving your travel needs in one stop”—character count 210, mobile displays as “Providing global popular travel destination guides, including Southeast Asi…”—users cannot see the key value of “one stop.”
- Positive Case: A food blog page description “10 home-cooked dishes even beginners can make, detailed steps, common ingredients, done in 30 minutes, with ingredient list and failure analysis included”—character count 142, fully displays pain points like “beginner-friendly,” “30 minutes,” and “failure analysis,” CTR is 28% higher than average.
Accurate Content Matching: The description must truthfully reflect page content, otherwise users will bounce quickly after clicking (Google will lower the ranking of such pages).
- Incorrect Example: A beauty page title is “2024 Summer Sunscreen Recommendations,” but the description reads “Winter Skincare Guide: Moisturizing Mask and Body Lotion Selection Guide”—users find mismatched content, bounce rate as high as 75% (Google Search Console data).
- Correct Example: Title “2024 Summer Sunscreen Recommendations: List for Oily/Dry/Sensitive Skin,” description “Testing 15 summer sunscreens, recommended by skin type, including film-forming time, water resistance, and ingredient safety comparisons, helping you choose sunscreen that won’t cause acne or tanning”—high consistency between description and content, bounce rate only 32%.
Include Call to Action (CTA): Use words like “Recommend,” “Attached,” “View” to guide user clicks (not mandatory, but effective).
- Ordinary Description: “This article introduces basic Python syntax.”
- Optimized Description: “A must-read for Python beginners! From variables and loops to functions, explaining basic syntax through 10 cases, with exercises and answers for download.”—the latter’s CTR is 20% higher than the former (A/B testing data).
A description is not a “keyword list,” but a “preview of the solution to the user’s problem.”
<meta name=”robots”>
The robots tag is the “action guide” for Google’s crawler. Incorrect settings can result in the page never being indexed (e.g., mistakenly adding noindex).
Common Directives and Use Cases (Based on Google Official Documentation):
| Directive Combination | Meaning | Use Case |
|---|---|---|
| index, follow | Allow page indexing and follow links on the page (Default) | All normal pages requiring indexing and weight transfer (e.g., Home, Product pages) |
| noindex, follow | Allow crawling but no indexing (Page won’t appear in search) | Temporary test pages, duplicate event pages (e.g., “Pre-Double 11 page” replaced later) |
| index, nofollow | Allow indexing but don’t follow links (Link weight won’t transfer) | Pages with many external links (e.g., Industry directories) where you don’t want to dilute weight |
| noindex, nofollow | Disallow crawling and link following (Page and links are “invalid”) | Sensitive pages (e.g., internal data reports), dead link pages (deleted but not 404’d) |
Common Errors:
- Duplicate noindex settings: An official corporate site added noindex in both the page header and HTTP header due to technical issues, resulting in the site not being indexed for half a year (Google Search Console showed “discovered – not indexed”).
- Misusing nofollow to restrict internal links: An e-commerce site added nofollow to all “Product Detail” links to prevent weight loss, causing new products to go undiscovered by crawlers and indexing to drop by 40%.
Verification Method: Use the “URL Inspection” tool in Google Search Console, enter the page URL, and check if the “Indexing status” and “robots tag” are correctly identified.
The core of the robots tag is “clearly telling Google the ‘reason for existence’ of the page”—don’t add noindex if it needs indexing, and don’t add nofollow if it needs to transfer weight.
<meta name=”viewport”>
Global mobile search share has reached 62% (StatCounter 2024), and incorrect viewport settings are a primary cause for mobile ranking drops (Google Mobile-First Indexing Guidelines).
Core Parameters and Roles:
width=device-width: Makes the page width equal to the device screen width (avoids layout distortion from default scaling).initial-scale=1.0: Sets the initial zoom ratio to 1:1 (prevents mobile phones from automatically shrinking the page, making text unreadable).maximum-scale=1.0, user-scalable=no(Optional): Disables manual user zooming (suitable for mobile-only pages, but use with caution as it affects accessibility).
Consequences of Incorrect Settings:
- A news app’s official site once set the viewport to
width=1024(fixed PC width), forcing mobile users to manually zoom in to read, resulting in a mobile bounce rate of 85% and mobile rankings dropping from page 3 to page 10 (Google Search Console data). - An e-commerce mini-program site failed to set
initial-scale=1.0, resulting in a default zoom of 0.5; users saw blurry text, and the CTR was 35% lower than similar pages.
Verification Method: Open the page in Chrome, press F12 for Developer Tools, select “Mobile Mode,” and check if the page fits the screen width and the text is clear.
The essence of the viewport is “letting mobile users view content comfortably without zooming,” which is a foundational metric for Google to evaluate mobile experience.
<meta charset=”UTF-8″>
Character encoding determines if page text displays correctly. Over 90% of websites globally use UTF-8 (W3Techs 2024), which is the only encoding recommended by Google.
Why Must You Use UTF-8?
- Avoid Garbled Text: If a page uses GBK encoding but declares UTF-8, Chinese characters will appear as “boxes”; conversely, UTF-8 pages parsed as GBK will also be garbled.
- Affects Crawling: Google crawler’s success rate for garbled pages is only 30% (compared to 95% for normal pages), which may lead to content not being correctly indexed.
Common Errors:
- A foreign trade website mistakenly declared
charset=ISO-8859-1for “compatibility with foreign users,” causing Chinese product descriptions to appear garbled and search rankings in China to disappear completely (Google Search Console showed “Content unparseable”). - A blog platform defaulted to GBK encoding, but an editor mistakenly saved an article as UTF-8, leading to garbled front-end display and a 60% increase in user complaints.
Verification Method: View page source code, check if the <meta charset> tag exists and is set to “UTF-8”; visit the page via mobile to confirm there is no garbled text.
UTF-8 is the “universal translator” that lets both Google and users “understand” your page.
Canonical URL Declaration and De-duplication of Multi-version Content
Google crawls trillions of webpages daily, of which approximately 30% contain duplicate content (Google Search Central 2023 data).
Duplicate content confuses Google: “Which version is the one the user most needs?” If handled poorly, it leads to a ranking drop for all related pages.
A real case: An e-commerce site failed to normalize URL parameters for “Product Detail” pages (e.g., “?from=home” and “?from=search”), resulting in 20 different URLs for the same product.
Google crawlers treated these as independent pages, and ultimately the ranking for that product category dropped from page 2 to page 10, with monthly traffic decreasing by 45% (Google Search Console data).
Canonical URL declarations (<link rel="canonical">) and multi-version content tagging (<link rel="alternate" hreflang>) are the solutions to these problems.
<link rel=”canonical”>
The role of the canonical tag is to specify the “official representative URL” of the current page.
Google will prioritize crawling and indexing this URL, and the weight of other duplicate pages will be consolidated into it.
3 Standards for Choosing a Canonical URL (Based on Google Official Guidelines):
| Standard | Description | Example |
|---|---|---|
| Simplicity | Avoid redundant parameters (e.g., tracking parameter “?utm_source=xxx”) | Choose “https://www.example.com/product” over “https://www.example.com/product?utm_source=weibo” |
| Stability | A URL that exists long-term (doesn’t change frequently) | Prioritize “https://www.example.com/blog/seo-guide” over “https://www.example.com/blog/seo-2023” |
| Content Relevance | The URL matches the current page content exactly | If the current page is “2024 iPhone 16 Review,” the canonical URL should point to the long-term address of the same review, not “2023 iPhone 15 Review” |
Common Application Scenarios and Operations:
1. PC vs. Mobile Pages:
A news site once set independent URLs for PC and mobile (e.g., PC version “https://www.news.com/article”, mobile version “https://m.news.com/article”).
Without canonical tags, Google treated both as duplicate content, and mobile page rankings were only 1/3 of the PC version (Ahrefs data).
Correct Practice: Add a canonical tag to the mobile page header pointing to the PC URL (or vice versa, depending on the primary device used by users):
<link rel="canonical" href="https://www.news.com/article">
2. URLs with Parameters (Filtering, Sorting):
An e-commerce platform product page has parameters like “Sort by price” and “Sort by sales” (e.g., “https://shop.example.com/shoes?sort=price” and “https://shop.example.com/shoes?sort=sales”).
These pages are highly similar; without normalization, Google might index one at random, potentially causing a mismatch when users search for “cheap sneakers.”
Correct Practice: Choose the basic URL without parameters as the canonical address (e.g., “https://shop.example.com/shoes”), and add canonical tags on other parameterized pages pointing to it:
<link rel="canonical" href="https://shop.example.com/shoes">
3. Paginated Content (e.g., Page 2, Page 3 of an article list):
A blog has 10 pages of lists (e.g., “https://blog.example.com/page/2”, “https://blog.example.com/page/3”). Without normalization, Google might only index the 1st page, leaving subsequent content unindexed. Users searching for “Latest 10 Tech Articles” might only see the first page.
Correct Practice: Add a canonical tag on all paginated pages pointing to the 1st page (or choose the main page based on content importance):
<link rel="canonical" href="https://blog.example.com/page/1">
Common Errors:
- Conflicting multiple canonical tags: An official corporate site added two different canonical tags in the same page due to a technical glitch (e.g., pointing to both “https://www.example.com” and “https://www.example.com/home”). Google could not identify them, and the page was not indexed for six months (Google Search Console showed “discovered – not indexed”).
- Canonical tag pointing to an irrelevant page: An education site incorrectly pointed the canonical tag of a course detail page to the homepage, causing the course page ranking to drop from page 5 to page 20 (A/B testing data).
Verification Method: Use the “URL Inspection” tool in Google Search Console, enter the page URL, and check if the “Canonical tag” shows the URL you set.
<link rel=”alternate” hreflang>
The hreflang tag is used to mark different language or regional versions of the same content (e.g., Chinese version, English version, US version, UK version).
Its core purpose is to let Google deliver the most relevant version to users in different regions, avoiding issues like “Chinese users seeing the English page” or “US users seeing the Australian version.”
Core Format and Rules:
- Must include the
hreflangattribute (value is language-region code, e.g., “zh-cn” for Simplified Chinese/China, “en-us” for US English). - Must point to the absolute URL of the corresponding version (including “https://”).
- All associated pages must cross-reference each other (Page A tags Page B, Page B tags Page A).
Example: Correct Tagging for a Multi-language Website
A multinational enterprise site has three language versions: Chinese, English, and Japanese:
- Chinese version:
https://www.global.com/cn - English version:
https://www.global.com/en - Japanese version:
https://www.global.com/jp
Each page must add the following tags in the header (taking the Chinese version as an example):
<link rel="alternate" hreflang="zh-cn" href="https://www.global.com/cn">
<link rel="alternate" hreflang="en-us" href="https://www.global.com/en">
<link rel="alternate" hreflang="ja-jp" href="https://www.global.com/jp">
Common Errors and Consequences:
- Incorrect Language Code: A travel site incorrectly marked “Simplified Chinese/China” as “zh-ch” (it should be “zh-cn”). Google failed to recognize it, and Chinese users might be served the English version during search, with a bounce rate as high as 65% (Google Analytics data).
- Missing Cross-referencing: A cross-border e-commerce site only tagged the English link on the product page, but the English page didn’t tag the Chinese version. Google deemed the association “insufficient,” and rankings for both versions dropped by 20% (Moz test data).
- Redundant Region Codes: A company created separate pages for “US English” and “UK English” but incorrectly marked both “en-us” and “en-gb” simply as “en” (too broad). Google couldn’t distinguish them, and users might receive a mismatched version (e.g., UK users seeing a page with US spelling).
Verification Method: Use Google’s “hreflang testing tool” (https://technicalseo.com/tools/hreflang/) to enter the page URL and check if all associated pages are correctly tagged.
Coordination between Canonical and hreflang
In actual operation, canonical and hreflang tags often need to be used together.
First, determine the “Main Version” via canonical, then use hreflang to mark different language/region versions. This is the key to avoiding confusion.
Case: Optimization Process of an International Education Institution
The institution’s official site had 3 language versions (Chinese, English, Spanish) and both PC/mobile pages, but previously had no normalization:
- The Chinese version had two URLs: “https://edu.example.com/cn” and “https://edu.example.com/cn?source=wechat”.
- The English PC page was “https://edu.example.com/en”, and the mobile page was “https://m.edu.example.com/en”.
Problems before optimization:
- Google treated “https://edu.example.com/cn?source=wechat” as an independent page, causing duplicate Chinese content and diluting the main version’s ranking.
- The mobile and PC versions were treated as different pages, so mobile users saw content that didn’t match the PC version (e.g., misaligned button positions).
Optimization Steps:
- Set Canonical Tags:
- All Chinese pages (including those with parameters) added a canonical tag pointing to “https://edu.example.com/cn”.
- The mobile English page added a canonical tag pointing to the PC version “https://edu.example.com/en”.
- Set hreflang Tags:
- The Chinese page marked “zh-cn” pointing to itself, while also linking to English and Spanish versions.
- The English PC page marked “en-us” pointing to itself, while also linking to Chinese and Spanish versions.
Optimization Results (After 3 Months):
- The ranking of the Chinese main page rose from page 5 to page 1, organic traffic increased by 80%.
- Mobile user bounce rate dropped from 70% to 45%, mobile ranking improved by 12 positions.
Optimization for Mobile Display
StatCounter 2024 data shows that global mobile search share has reached 62%, surpassing PC as the primary search scenario for users.
However, a 2023 Google analysis of crawl logs from 100,000 websites found that 70% of mobile pages have “display issues”—overlapping text, overlapping buttons, and image overflows, leading to a 30% increase in bounce rate (Google User Behavior Research Report).
A real-life case: A local life service platform failed to correctly set the mobile viewport. When mobile users visited, the page text was compressed into “tiny ants,” and buttons required zooming in 3 times to be clickable.
The mobile bounce rate for that page was as high as 82%, and average monthly mobile traffic was 55% less than similar well-adapted pages (Google Search Console backend data).
The Viewport Tag
The viewport tag (<meta name="viewport">) is the core configuration for mobile display. Its role is to tell the browser “how to scale the page to fit the phone screen.”
Incorrect settings will lead to blurry text and overlapping buttons, directly reducing user dwell time.
Core Parameters and Their Effects (Based on W3C standards):
| Parameter | Recommended Value | Role | Error Example & Consequences |
|---|---|---|---|
width | device-width | Sets page width equal to the device screen width (prevents default scaling) | Set to a fixed value (e.g., width=1024): Users must zoom manually to read; bounce rate increases by 40% (A/B testing) |
initial-scale | 1.0 | Initial zoom ratio of 1:1 (prevents default shrinking) | Set to 0.5: Text is too small; user conversion rate drops by 25% (Google Analytics) |
maximum-scale | 1.0 (Optional) | Prevents users from manually zooming (suitable for mobile-only designs) | Set to 5.0: Users might zoom accidentally, causing layout issues and affecting readability |
user-scalable | no (Optional) | Disables manual zooming (use with caution as it affects accessibility) | Set to yes: Some users may zoom in, breaking design consistency |
Practical Advice:
- Beginners should use the standard configuration:
<meta name="viewport" content="width=device-width, initial-scale=1.0">. - If the page contains many images or charts, you can add
maximum-scale=1.0to prevent accidental zooming that distorts images.
Flexible Layout is Safer than “Fixed Pixels”
Mobile screen sizes vary significantly (from 4 to 7 inches). Defining container widths with “fixed pixels” (e.g., width: 300px) leads to content overflow on small screens and excessive whitespace on large screens.
Flexible Layout (Flexbox) or percentage-based layouts adapt automatically to different screens and are the core solutions for mobile typography.
Comparative Test Data (Statistics by Ahrefs on 200 mobile pages):
| Layout Method | Text Overlap Rate | User Dwell Time | Bounce Rate |
|---|---|---|---|
| Fixed Pixel Layout | 42% | 12 seconds | 78% |
| Flexible Layout (Flexbox) | 8% | 28 seconds | 35% |
Specific Implementation Methods:
- Replace fixed widths with
max-width: 100%for containers to ensure they don’t exceed screen width. - Set text line height to
1.5emor more (e.g.,line-height: 1.6) to avoid crowded text on small screens. - Use
width: 100%; height: autofor images to let them scale automatically with container width.
Negative Case: A food blog list used fixed pixel width (width: 700px). On a 5-inch phone, text was compressed into a single vertical line, requiring users to scroll horizontally to read. The bounce rate was as high as 85% (Google Search Console).
Positive Case: An e-commerce app product detail page used Flexbox (display: flex). Images and text adapted automatically, and user dwell time increased from 15 to 40 seconds, with a 22% increase in conversion rate.
Click Targets Should Be at Least 48×48 Pixels
Mobile users operate via finger taps. If buttons are too small (e.g., 30×30 pixels), users easily miss the target or click adjacent buttons, leading to failed operations and a poor experience.
Google recommends a minimum click target size of 48×48 pixels (based on human-computer interaction research).
Correlation Between Click Target Size and User Behavior (Google User Research Lab):
| Button Size (Pixels) | Misclick Rate | Time to Complete Action | User Satisfaction (1-5) |
|---|---|---|---|
| 30×30 | 35% | 8 seconds | 2.1 |
| 48×48 | 8% | 3 seconds | 4.5 |
| 60×60 | 3% | 2 seconds | 4.8 |
Practical Advice:
- Set navigation and form submission buttons to at least
48px × 48px(usemin-widthandmin-height). - Maintain at least
16pxspacing between buttons to avoid accidental triggers. - Text on buttons (e.g., “Buy Now”) should have a font size of at least
16pxfor better legibility.
Case Study: A banking app login page had a “Login” button sized 36px × 36px. The probability of users accidentally hitting “Forgot Password” was 40%. After resizing to 48px × 48px with 16px spacing, the misclick rate dropped to 5%, and login success rate improved by 28%.
“Slow Image Loading”: Coordinate Viewport and Lazy Loading
Mobile network environments are unstable. If images are not adapted for mobile sizes or load too slowly, users will leave.
Coordinating viewport settings with lazy loading can significantly improve loading speed.
Impact of Slow Image Loading (Akamai 2024 Mobile UX Report):
| Load Time (Seconds) | Bounce Rate | Conversion Rate |
|---|---|---|
| ≤2s | 18% | 5.2% |
| 3-5s | 45% | 2.1% |
| ≥6s | 72% | 0.8% |
Optimization Methods:
- Control image width via viewport: Use
width=device-width(or CSSmax-width: 100%) to avoid loading massive PC-sized images (e.g.,1920px × 1080px). - Enable Lazy Loading: Load images only when they enter the viewport (Google supports native
loading="lazy").
Sample Code:
<img src="product.jpg" alt="Product" loading="lazy" width="600" height="400">.
Case Study: A travel website loaded high-def PC images (2000px × 1500px), resulting in 8-second mobile load times and a 75% bounce rate. After optimization (capping width at 100%, using mobile-sized 600px × 450px images, and lazy loading), load time dropped to 2 seconds, bounce rate fell to 20%, and mobile traffic grew by 60%.
Testing Tools to Identify Issues
Mobile adaptation issues like overlapping text or misaligned buttons can be missed by the naked eye. Professional tools help locate and fix these problems quickly.
| Tool Name | Function | Steps |
|---|---|---|
| Chrome DevTools | Simulate different phone models (e.g., iPhone 15, Samsung S24) | 1. Right-click → “Inspect”; 2. Click “Toggle Device Toolbar” (Ctrl+Shift+M); 3. Select phone model. |
| Lighthouse | Generate mobile performance reports (Adaptability, Click Targets, etc.) | 1. Open DevTools → “Lighthouse”; 2. Check “Mobile” → Generate report. |
| BrowserStack | Test on real mobile devices (iOS, Android models) | 1. Visit website; 2. Select target phone model; 3. Enter URL to view. |
Case Study: An education platform discovered their “Course Categories” button was covered by an image when simulating an iPhone 15. By adjusting the CSS z-index, the problem was fixed, and mobile conversion rate increased by 19%.
Controlling Social Media Sharing Previews
On social media, the sharing preview (Title + Description + Cover Image) determines 80% of whether a user clicks (Meta 2023 User Behavior Report).
After optimization, a headline changed to “2024 AI Trends: Detailed Analysis of LLMs, Multimodality, and Industry Implementation” and the cover was replaced with a 1200×630 pixel HD image, the click-through rate jumped to 12%.
Open Graph (OG) Tags
Developed by Facebook, OG tags are now the global standard for social platforms like LinkedIn and Pinterest. They tell the platform: “This is how the title, description, and image should look.”
4 Essential OG Properties and Optimization Rules:
| Property | Role | Recommendation | Error & Consequence |
|---|---|---|---|
og:title | Preview Title | ≤60 characters. Include core keywords. | Title truncated: CTR drops 25%. |
og:description | Preview Summary | ≤160 characters. Use specific numbers/pain points. | Vague description: CTR only 1.5%. |
og:image | Preview Image | ≥1200x630px. High quality, under 5MB. | Tiny image (100×100): 70% skip rate. |
og:url | Target URL | Use absolute paths (https://). | Broken URL: 404 error, damages credibility. |
Twitter Cards
Twitter Cards are specific to Twitter, offering a more “lightweight” system for short text and images.
3 Essential Twitter Card Properties:
| Property | Role | Recommendation |
|---|---|---|
twitter:card | Card Type | Use summary_large_image for high engagement. |
twitter:title | Twitter Preview Title | ≤70 characters. |
twitter:image | Twitter Preview Image | 1200x675px (16:9 ratio). |
The “SEO Value” of Social Sharing Previews
While not a direct ranking factor, high-engagement social shares indirectly boost SEO. High social interaction signals to Google that the page is popular and relevant, leading to better authority and rankings over time.
Other Functional Meta Tags
Functional meta tags handle character encoding, browser compatibility, and redirection. While “secondary,” they affect how Google crawls your content.
<meta charset=”UTF-8″>
Character encoding ensures text is displayed correctly. UTF-8 is the Google-recommended universal standard.
- Avoid Garbled Text: Incorrect encoding turns Chinese/special characters into “???”.
- Impact Crawling: Google’s success rate for crawling garbled pages is only 30%.
<meta http-equiv=”X-UA-Compatible” content=”IE=edge”>
Tells Internet Explorer to use the latest rendering engine. This is crucial for corporate or government environments that still utilize legacy browsers.
<meta http-equiv=”refresh”>
Used for auto-redirection. Google generally discourages this as it can be perceived as spammy behavior. Use 301 server-side redirects instead whenever possible.
<meta name=”referrer”>
Controls the “Referer” header information sent to other sites. Essential for balancing user privacy with data analytics.
In conclusion, SEO meta tags exist not just to “please the algorithm,” but to ensure both Google and users can “smoothly use your website.”
