Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Utf-8 symbols in the Title or Meta Description?
- 
					
					
					
					
Has somebody any experience (pros or cons) to using utf-8 symbols in the Title or in the Meta Description tags?
Expedia uses it:
http://prntscr.com/74ofrv - 
					
					
					
					
Google is officially supporting some emoticons. I talked to one big-brand SEO last week who has tested it with a fair degree of success. A couple of warnings:
(1) Testing the impact on one title tag is a fair amount of work, so it really has to be a high-impact SERP. This isn't something you want to spend days on across thousands of results.
(2) Make sure the character/symbol really is relevant. People focus on the first two words of a headline, and that emoticon may well take the place of one of those words, so make it count. I wouldn't do this just because you can.
(3) Not all characters render properly on all OSs and devices. Make sure to test.
 - 
					
					
					
					
Thanks for your Answer Ikkie, but my question was especially about using "utf-8 symbols in the Title/Meta tags".
Should I use, or not? - 
					
					
					
					
that there are no real pros or cons in where you place the
TITLEelement within the HTML document’s HEAD area. However, although this is nothing whatsoever to do with SEO, I do remember reading that in an HTML document, the best practise is to include theTITLEafter the firstMETAtag that declares the content-type and/or charset value(s), e.g.:<code><title>[Placeholder Title]</title> […]</code>(I am fairly certain that this technique is stated somewhere in the W3C Recommendation, HTML 4.01 Specification, in the section "The global structure of an HTML document" ( …but if I would double-check this.) Although I think the technical reason was to ensure titles that contain HTML entities that need to be escaped should always declare a character set before you provide the actual text, it still makes you think: is source-ordering important?
At the very least, it is conventional wisdom to always place the content you want to gain the most exposure in terms of SEO/the search-engines' results pages (SERPS) higher up in the web pages (X)HTML source code (e.g. in a website without any
METAdescription tags set, the first paragraph in the document will probably be the one chosen to represent that webpage’s description in its SERP listing, not the second or third etc., etc.) Ultimately, I would say that you certainly have nothing to lose in placing thisTITLE(or any content) higher.You can also see the guidelines for this on the MOZ blog link here
https://a-moz.groupbuyseo.org/blog/15-tips-to-speed-up-your-website
 
Browse Questions
Explore more categories
- 
		
		
Moz Tools
Chat with the community about the Moz tools.
 
- 
		
		
SEO Tactics
Discuss the SEO process with fellow marketers
 
- 
		
		
Community
Discuss industry events, jobs, and news!
 
- 
		
		
Digital Marketing
Chat about tactics outside of SEO
 
- 
		
		
Research & Trends
Dive into research and trends in the search industry.
 
- 
		
		
Support
Connect on product support and feature requests.
 
Related Questions
- 
		
		
		
		
		
		
How does Google handle fractions in titles?
Which is better practice, using 1/2" or ½"? The keyword research suggests people search for "1 2" with the space being the "/". How does Google handle fractions? Would ½ be the same as 1/2?
Intermediate & Advanced SEO | | Choice2 - 
		
		
		
		
		
		
No index detected in robots meta tag GSC issue_Help Please
Hi Everyone, We just did a site migration ( URL structure change, site redesign, CMS change). During migration, dev team messed up badly on a few things including SEO. The old site had pages canonicalized and self canonicalized <> New site doesn't have anything (CMS dev error) so we are working retroactively to add canonicalization mechanism The legacy site had URL’s ending with a trailing slash “/” <> new site got redirected to Set of url’s without “/” New site action : All robots are allowed: A new sitemap is submitted to google search console So here is my problem (it been a long 24hr night for me 🙂 ) 1. Now when I look at GSC homepage URL it says that old page is self canonicalized and currently in index (old page with a trailing slash at the end of URL). 2. When I try to perform a live URL test, I get the message "No: 'noindex' detected in 'robots' meta tag" , so indexation cant be done. I have no idea where noindex is coming from. 3. Robots.txt in search console still showing old file ( no noindex there ) I tried to submit new file but old one still coming up. When I click on "See live robots.txt" I get current robots. 4. I see that old page is still canonicalized and attempting to index redirected old page might be confusing google Hope someone can help to get the new page indexed! I really need it 🙂 Please ping me if you need more clarification. Thank you ! Thank you
Intermediate & Advanced SEO | | bgvsiteadmin1 - 
		
		
		
		
		
		
Duplicate Title tags even with rel=canonical
Hello, We were having duplicate content in our blog (a replica of each post automatically was done by the CMS), until we recently implemented a rel=canonical tag to all the duplicate posts (some 5 weeks ago). So far, no duplicate content were been found, but we are still getting duplicate title tags, though the rel=canonical is present. Any idea why is this the case and what can we do to solve it? Thanks in advance for your help. Tej Luchmun
Intermediate & Advanced SEO | | luxresorts0 - 
		
		
		
		
		
		
Exact match Title and H1 tags, and over optimization
Hi Mozzers - was just wondering whether matching H1 and Title tags are still OK, or whether there's an over optimization risk if they exact match?
Intermediate & Advanced SEO | | McTaggart0 - 
		
		
		
		
		
		
Pipe ("|") in my website's title is being replaced with ":" in Google results
Hi , One of the websites I'm promoting and working on is www.pau-brasil.co.il.
Intermediate & Advanced SEO | | Kadel
It's wordpress-based website and as you can see the html's Title is "PauBrasil | some hebrew slogan".
(Screenshot: http://i.imgur.com/2f80EEY.gif)
When I'm searching for "PauBrasil" (Which is the brand's name) , one of the results google shows is "PauBrasil: Some Hebrew Slogan" (Screenshot: http://i.imgur.com/eJxNHrO.gif ) Why does the pipe is being replaced with ":" ?
And not just that , as you can see there's a "blank space" missing between the the ":" to the slogan.
(note: the websites has been indexed by google crawler at least 4 times so I find it hard to believe it can be the reason) I've keep on looking and found out that there's another page in that website with the exact same title
but when I'm looking for it in google , it shows the title as it really is , with pipe. ("|").
(Screenshot: http://i.imgur.com/dtsbZV2.gif) Have you ever encountered something like that?
Can it be that the duplicated title cause that weird "replacement"? Thanks in advance,
Kadel0 - 
		
		
		
		
		
		
Meta NoIndex tag and Robots Disallow
Hi all, I hope you can spend some time to answer my first of a few questions 🙂 We are running a Magento site - layered/faceted navigation nightmare has created thousands of duplicate URLS! Anyway, during my process to tackle the issue, I disallowed in Robots.txt anything in the querystring that was not a p (allowed this for pagination). After checking some pages in Google, I did a site:www.mydomain.com/specificpage.html and a few duplicates came up along with the original with
Intermediate & Advanced SEO | | bjs2010
"There is no information about this page because it is blocked by robots.txt" So I had added in Meta Noindex, follow on all these duplicates also but I guess it wasnt being read because of Robots.txt. So coming to my question. Did robots.txt block access to these pages? If so, were these already in the index and after disallowing it with robots, Googlebot could not read Meta No index? Does Meta Noindex Follow on pages actually help Googlebot decide to remove these pages from index? I thought Robots would stop and prevent indexation? But I've read this:
"Noindex is a funny thing, it actually doesn’t mean “You can’t index this”, it means “You can’t show this in search results”. Robots.txt disallow means “You can’t index this” but it doesn’t mean “You can’t show it in the search results”. I'm a bit confused about how to use these in both preventing duplicate content in the first place and then helping to address dupe content once it's already in the index. Thanks! B0