Welcome to the Q&A Forum

It could end up outranking the homepage depending on how many links you have pointing to the page in question and how well optimized your homepage is for the keyword. Rather than focusing on ranking this page because of the URL though, I would focus on ranking the page that provides the best user experience. If the homepage is too broad to provide a good UX then maybe a separate landing page does make sense. If you're trying to outrank the homepage, the two things you have the most immediate control over are:

• decreasing the amount of times you use the keyword in prominent places on the homepage
• increasing the amount of internal links pointing to this other landing page

Best,

Daniel

Hi there,

It's certainly possible for a page to outrank the homepage for a keyword they're both targeting depending on both external and internal links pointing to it. As you point out, internal links are an important signal to Google about the importance of a relative page.

Ideally you wouldn't have multiple pages targeting the same keyword but if you do, you would likely want to leverage your internal links to influence which page actually ranks in Google if you have a preference.

Hope this helps!

Daniel

+1 to Mike and using "Fetch and Render". I would add using the inspect element in Chrome, along with looking at the cache like you did - you should be good to go if these all point to JavaScript being executed properly by Google.

Hope this helps!

You've got most of the main tools covered but you could try ubersuggest, the new Moz keyword tool or semrush too. Semrush is particularly great for competitive research - filter for a landing page and see what keywords it ranks for. You could also filter for keywords that include "model" if you're interested in only those.

Hope this helps!

Hey Roderick,

It looks like the dates are no longer showing in the SERPs (at least on my end). Either way, I wouldn't get too hung up on the dates contributing to lower rankings, it's the likely the result of many other factors. Sorry this answer isn't more helpful but I would focus on other areas your site can improve on from an SEO perspective rather than the date.

Hi there,

Pre-render sounds like your best option here. Feel free to PM me a link to your site though and I can take a closer look if you'd like.

Best,

Daniel

Hey Andy,

Could you use a self-referencing canonical that points back to the page itself (without irrelevant parameters) rather than the first page of the series? This is what amazon does. Ie: example.com?page-2&id=123 canonicals back to example.com?page-2

This is also what Google recommends: https://support.google.com/webmasters/answer/1663744?hl=en

Hi Lauren,

JSON is usually an easy way to implement schema tags because you can add them to the section of a page instead of adding them inline element by element. This can make it simpler to roll out schema tags at scale. Theoretically the different ways you implement schema tags shouldn't affect the outcome, only the ease of implementing them.

Hope this helps!

Just to jump off what Nicolas has said - are you all set up at Google News Publisher Center? This is an important part of being promptly featured in Google News.

Hi there,

This is odd, 4 weeks is a long time and something is likely going wrong. Are you positive that your 301s have been implemented correctly? Have you received any messages in Search Console/GWT that are relevant?

I would also do as Ikkie suggests and submit prominent URLs which have yet to be indexed here: https://support.google.com/webmasters/answer/6259634?hl=en

Please let me know if these checks fail or if you'd like to PM me the URL and I'll take a closer look.

Hope this helps,

Daniel

Hi there,

Does the page have a canonical tag pointing back to itself? That should help if not. Feel free to PM me the site in question and I can take a closer look too.

Daniel

+1 to what Danny said. A couple other thoughts:

• +3000 4xx client errors: do any of these have many links or a significant amount of traffic? If not and they aren't a large portion of your overall site, it's not a big deal.
• **+3000 duplicate content issues: **as Danny said, there is likely a trend here, try to identify it and resolve it in mass rather than going page by page.
• **+35000 temporary redirects: **are any of these temporary redirects to important pages? If so, it's worth changing them to 301s. However, if they are all pointing to old, deep and weak pages then it's likely not a big concern again.

Daniel

Hi there,

I would go with option #1 and use CSS to improve the design of the table. You can then use JavaScript to add functionality if necessary without the risk of some content being un-indexable.

Some examples of nicely designed tables using HTML and CSS: https://www.freshdesignweb.com/free-css-tables/

Sorry for the delay Taysir, I didn't see the PM. I took a look at your site though and your implementation of the drop down menu is good and both Bing and Google are indexing it correctly. Hope this helps!

Hi there,

Do you mind sharing the URL of the site in question? It would help to understand how the nav is actually being implemented.

Hi there,

You're right that setting up Schema tags is necessary (I'd recommend using JSON-LD). It won't guarantee a rich snippet but it's the best you can do.  You can also use this tool to validate your structured markup: https://developers.google.com/structured-data/testing-tool/

It's definitely doable to pull in this data automatically instead of manually adding it each week but you'll have to talk with the client's engineering team about the specific implementation for this. I don't know of any out of the box software solution unfortunately.

The fetch as Googlebot function in GWT is definitely your best bet here.

Most JavaScript dropdowns I've run into are being indexed properly by Google by now but if your particular JS implementation isn't being executed when fetching as Googlebot, then you'll need to use a solution like prerender.

Hey there,

As long as the redirect is implemented properly and only affects registered users, it should not have an effect on your SEO. Just make sure you test it after rolling it out.

However, one consideration would be that existing customers will not be able to see the regular homepage, which means:

• it'll be harder for them to link to the homepage if they can't figure out what's going on
• there might be information on the homepage that they want to access but can't

Therefore, I'd recommend having a way for registered users that were redirected to the dashboard to have an intuitive way of visiting the homepage without being redirected.

Just wanted to +1 EGOL's answer. I would add the PDFs to your sitemap; it shouldn't take much work to index them and they should definitely capture organic traffic.

No worries. In the case of redirecting from one page to multiple pages, I would recommend redirecting your Blogger site to the most relevant page on your new WordPress site - which will likely be your homepage.

That being said, make sure you have good reasons for moving over to WordPress in the first place.

If a 301 redirect is implemented correctly, your new WordPress site should more or less replace your old Blogger site in the SERPs - although it might take a couple weeks. Therefore, the traffic that goes to your Blogger site would now flow to your WordPress site.

Hi there,

If you plan to move over to WordPress then I would recommend using using a 301 redirect and migrating your site completely. I wouldn't recommend trying to maintain both your Blogger and WordPress sites if they serve the exact same purpose - choose one to host all your content and redirect the other one to it (using a 301 not a 302).

Also, any content you put in an iFrame won't be indexed so you wouldn't be receiving SEO benefit from that content on your Blogger site.

Hope this helps!

Hey, no worries and you're right that your filters should block them as well. Using .htaccess would be just an additional defense mechanism but may not be necessary.

I would use your .htaccess file to block them with the following code (this would for example block referrals from semalt.com and semalt.com subdomains):

RewriteEngine On

Options +FollowSymlinks

RewriteCond %{HTTP_REFERER} ^https?://([^.]+.)*semalt.com\ [NC,OR]

RewriteRule .* – [F]

You can also use .htaccess to block IP addresses associated with the spammy sources.

edit: just saw your edit but hope this helps nevertheless!

Hi there,

You’re on the right track and the best way to retroactively remove spammy sources is through report filters and advanced segments.

A couple other notes:

• A good way to spot spammy referrers is to sort by bounce rate and eliminate any with 100% bounce and over 10 sessions.
• Avoid using the “referral exclusion list” since this will just count spam traffic as direct traffic instead.
• You should also enable the GA ‘bot filtering’ feature under ‘Reporting view settings’ as seen here