I was hoping the layout builder would fix some SEO issues we have for quite some time. Unfortunately, it looks like the issues are still there. Using the new post archive layout + the post pagination element, there seems no way to add anchor text anywhere? Am I missing something here?
Checking the page for SEO errors bring up the below.
Checking the remarks, turns out they are pointing to the paging element.
Hi Ruud,
The Anchor Text is in the pagination links. There might be a few different reasons behind your issue, can you please enlist your site into your Themeco account to further check and mention the tool used to get the report shown in the screenshot.
To know more on the Anchor Text, please go through the following articles:
Thanks
Hello @tristup, I have added the site info as you requested.
The tool used is this SEO Tool
I checked the page source:
Hello Ruud,
You are referring to the incorrect tag.
Please be aware that the <link> tag defines the relationship between the current document and an external resource.
What you should look at in relation to your link text is this:
And the tool is not giving correct information because if you look closely at the code, it has this:
<nav class="e6118-12 x-paginate" role="navigation">
<div class="x-paginate-inner">
<span aria-current="page" class="page-numbers current">1</span>
<a class="page-numbers" href="https://evolinestore.com/news/page/2/">2</a>
<a class="page-numbers" href="https://evolinestore.com/news/page/3/">3</a>
<a class="page-numbers" href="https://evolinestore.com/news/page/4/">4</a>
<span class="page-numbers dots">…</span>
<a class="page-numbers" href="https://evolinestore.com/news/page/7/">7</a>
<a class="page-numbers" href="https://evolinestore.com/news/page/8/">8</a>
<a class="next page-numbers" href="https://evolinestore.com/news/page/2/"> <i class="e6118-12 x-icon" aria-hidden="true" data-x-icon-s=""></i> </a>
</div>
</nav>
Based on the code above, the 2, 3, 4, 7, 8 and the arrow is an anchor text.
Hope this helps.
Ahhh, you are correct Rue.
I was mislead by the SEO tool, I will inform them about this issue in their tool.
Thanks for clearing this.
Howdy, @ruudvanbeek! No worries…another point I wanted to just leave here before closing this out is that the Pagination Elements included in our last major release are all powered by core WordPress functionality, so nothing here is custom as we’re trying to lean into WordPress’ way of doing things as much as possible. We don’t have much control over the general output of the content in the pagination as it’s all handled by the core framework, but that means that is more than likely adhering to any proper SEO standards for semantic / accessible markup due to the nature of it being produced and maintained by the core WordPress team (and any potential issues if there were some would come in the form of a WordPress update down the road).
Cheers!
Hello @kory, I think this is the best way to go by “leaning” into the wordpress way of doing things.
Unfortunately, there still might be something here that is somehow not quite compatible yet…? Below is the response I received from support of the SEO tool:
Might they have some point here…? The icon looks like provided as x-icon.
Hello Ruud,
I will be adding this to our issue tracker so that @Kory and @Alexander can address this.
Please bear with us.
@ruudvanbeek, I have pushed a fix for this, which will go out whenever our next release is put out. I did not opt for the title attribute being used as this is a dated approach for search engine optimization purposes, which you can read up on from various resources online if you’d prefer:
Instead, what I have done is output the values specified in the Text inputs as “screen reader text” within the previous / next buttons if the Icon option is chosen. This means that this text will be available to screen readers / search engine bots as readable, meaningful text, but will remain visually hidden from anyone else. If you wish to update these values, simply click over to the Text version of the Pagination Element and update their values in the inputs, then switch back to Icon and those updated values will be reflected in the markup. Again, this is not live at the moment but will go out in a coming release, so keep an eye out for that when available.
Cheers!
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.
