In Crawl Diagnostics, length of title element is incorrect
-
Hey all,
It appears the Moz crawler is misreading the number of characters in my website's page titles. It shows 72 characters for the following page's title element:
http://giavan.com/products/orange-crystal-chain-necklace-with-drop
The page title for this web page is: Orange Crystal Chain Necklace with Drop | Giavan
which is 48 characters. As it stands, this page title is displayed at 48 characters in Google SERPs.
I am getting "This Element is Too Long" issue on 925 pages, which is just about the entire site. These issues appeared after I added additional Shopify (Liquid) code to the page title. If you inspect the code, you will see title element looks a bit odd with extra spacing and line breaks.
What I'd like to know is whether or not it's necessary to rewrite the Shopify code, for SEM purposes. My feeling is that it's okay because the page titles look fine in SERPs but those 925 Moz crawl errors are kind of scary.
Thanks for your help!
-
This appears to have fixed the problem, thank you. Had to add a non-breaking space before {% endif %}{{ page_title }} but from what I can tell, your solution resolved the character count discrepancy. I expect this will be validated when Moz re-crawls the site.
-
Ok this might help without changing any code really. The way most templating languages work is they preserve spaces and returns between statements so they can be formatted correctly. Just put your code on one line like this
{% if current_tags %} {{ current_tags | join: ', ' | capitalize }}{% endif %}{{ page_title }}{% if current_page != 1 %} – Page {{ current_page }}{% endif %}{% unless page_title contains shop.name %} | {{ shop.name }}{% endunless %}
With no spaces in between. Then test it, if everything is run together just a space between the variable. But that should take out the hard returns and return your title tag on one line like normal.
-
Here is the liquid code. It inserts tags like "Red" and "Teardrop" into the page title to make the page title more descriptive.
<title><br /> {% if current_tags %} {{ current_tags | join: ', ' | capitalize }}{% endif %}<br /> {{ page_title }}<br /> <br /> {% if current_page != 1 %} – Page {{ current_page }}{% endif %}<br /> {% unless page_title contains shop.name %} | {{ shop.name }}{% endunless %}<br /></title>
Thanks so much for helping me out with this.
-
The post by Tiffany is correct, but most crawlers like moz work on string length. What the issue looks like is that the template is sending out a lot of white space that is being counted in the string length. Where this comes into play and why it is not noticeable is this. In html if you have two spacebar spaces, it will only render as one space in viewports. But in the code you will still have the two spaces.
The best solution to fix what you have would be to try to attach a filter to your current code, thus reducing the number of blank spaces and line breaks. Can you past what liquid code you currently have to generate the page title and I might can work something out to test. I haven't used liquid before, but it looks close enough to smarty that I might could work something out.
-
It is my understanding that it is based on pixels and not so much characters count. For example:
mommy
little
Mommy is only 5 characters, while Little is a whole character more. However, it is the actual distance, not the character count. At least that is my understanding.
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
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
-
URL Length Issue
MOZ is telling me the URLs are too long. I did a little research and I found out that the length of the URLs is not really a serious problem. In fact, others recommend ignoring the situation. Even on their blog I found this explanation: "Shorter URLs are generally preferable. You do not need to take this to the extreme, and if your URL is already less than 50-60 characters, do not worry about it at all. But if you have URLs pushing 100+ characters, there's probably an opportunity to rewrite them and gain value. This is not a direct problem with Google or Bing - the search engines can process long URLs without much trouble. The issue, instead, lies with usability and user experience. Shorter URLs are easier to parse, copy and paste, share on social media, and embed, and while these may all add up to a fractional improvement in sharing or amplification, every tweet, like, share, pin, email, and link matters (either directly or, often, indirectly)." And yet, I have these questions: In this case, why do I get this error telling me that the urls are too long, and what are the best practices to get this out? Thank You
Moz Pro | | Cart_generation1 -
Why Only Our Homepage Can Be Crawled Showing a Redirect Message as the Meta Title
Hello Everyone, So recently when we checked our domain using a Moz Crawl Test and Screaming Frog only the homepage comes up and the meta title says “You are being redirected to…”. We have several pages that used to come up and when submitting them to GSC no issues come up. The robots.txt file looks fine as well. We thought this might be ‘server’ related but it’s a little out of our field of expertise so we thought we would find out if anyone has any experience with this (ideas of reasons, how to check…etc.) or any potential suggestions. Any extra insight would be really appreciated. Please let us know if there is anything we could provide further details for that might. Looking forward to hearing from all of you! Thanks in advance. Best,
Moz Pro | | Ben-R0 -
Initiate crawl
Anyway to start the crawl of a site immediately after changes have been made? Or must you wait for the next scheduled crawl? Thanks.
Moz Pro | | dave_whatsthebigidea.com0 -
Can Google see all the pages that an seomoz crawl picks up?
Hi there My client's site is showing around 90 pages indexed in Google. The seomoz crawl is returning 1934 pages. Many of the pages in the crawl are duplicates, but there are also pages which are behind the user login. Is it theoretically correct to say that if a seomoz crawl finds all the pages, then Google has the potential to as well, even if they choose not to index? Or would Google not see the pages behind the login? And how come seomoz can see the pages? Many thanks in anticipation! Wendy
Moz Pro | | Chammy0 -
Why does SEO moz show so many more duplicate page titles than webmaster
My SEO moz duplicate page titles are more than double the webmaster duplicate page titles. Plus, some of the items appearing in SEO moz are not really duplicates. Anyone else seeing this?
Moz Pro | | Stamats0 -
Duplicate Page Titles and Content
The SeoMoz crawler has found many pages like this on my site with /?Letter=Letter, e.g. http://www.johnsearles.com/metal-art-tiles/?D=A. I believe it is finding multiple caches of a page and identifying them as duplicates. Is there any way to screen out these multiple cache results?
Moz Pro | | johnsearles0 -
SEOMoz Crawl Warnings, do they really hurt rankings?
SEOMoz reports 250 crawl warnings on my site. In most cases its too long title tags, with 4 of them its missing meta description. SEOMoz says it will hurt my rankings? However, I'm sure a recent whiteboard Friday contradicted this. So what is it?
Moz Pro | | sanchez19600 -
Will canonical tag get rid of duplicate page title errors?
I have a directory on my website, paginated in groups of 10. On page 2 of the results, the title tag is the same as the first page, as it is on the 3rd page and so on. This is giving me duplicate page title errors. If i use rel=canonical tags on the subsequent pages and href the first page of my results, will my duplicate page title warnings go away? thanks.
Moz Pro | | fourthdimensioninc0