Welcome to the Q&A Forum

Hi Patrick, Thanks! Excellent answer, only a doubt about Schema, If every product is refreshing every month what happened with that information or could be a dynamic information for Schema?

I should have also mentioned the linking structure within the site. All 23 versions of the product are linked from within 1 category that contains roughly 70 products. This is why the products must be kept separate. So users can browse the different specs alongside other products with similar comparable specs in the same category. An example can be found here:  https://goo.gl/5L4cpK (its a little unordered at the moment but will be more organised soon) Take the 572 series, on the page above, it has 11 variations, the link currently filters the results on the page all 11 models are currently canonical'd to one version of the page. The filter also produces a category page that isn't linked on the website   (https://goo.gl/c53sBY) This page is currently no-indexed. How is the following for a solution? Turn the 572 series filter link into a link to the 572 category page (https://goo.gl/c53sBY) Change this page to be indexed and make its description a detailed guide to the full 572 series listing all models, options etc as you suggest Make all the 572 products canonical of this super descriptive all singing and dancing page

Don't get too caught up in jamming keywords into your titles. Chances are your competitors are already doing this, so use the opportunity to stand out and grab the users' attention; give them a reason to click your result over the other ~9 on the page. Page titles should be compelling so getting your keyword(s) in there is great, but try to avoid the clunk old [keyword] [keyword] page title style. Sometimes it makes sense and is about all you can really do but if you can avoid it, do so. I don't agree that you need to have the word Australia in the title either, Google looks at plenty of factors to determine what country you're in so no need to take up those precious pixels in your title with a long, redundant word! There are a couple of Whiteboard Fridays that cover this general topic which you might find helpful: Headline Writing and Title Tag SEO in a Clickbait World Keyword Targeting, Density, and Cannibalization I'd give you an example of a strong title but I just realised how little I know about wedding dresses! Basically, it should be something like Amelie Wedding Dress - [Something compelling; what do they care about?]. Remember, don't talk about yourself or your product, talk about the benefits these customers care about. If they're sold online, ship fast and this is your strongest selling point, maybe something like Amelie Wedding Dresses - Easy Online Store, Shipped in 48hrs!

No prob, let me know how things turn out (professional curiosity) Like yourself my main project is dated in areas and a workaround is more cost effective than a rebuild, always interesting to see how people get around issues. GL!

I wouldn't consider it keyword stuffing, reads pretty naturally, but it also looks like the same thing everyone else does... how would that stand out in these SERPs? What would make someone click yours over someone else's on this ultra dull list? Literally no one stands out. VrCVt58.png

It dosen't have any backlinks but I'm stumped as to why it isn't ranking higher than what it is, I'm not expecting 1st position but outside of the top 50 is something else. No backlinks and a recent domain registration date are big answers to your question.  This isn't an especially difficult SERP, but a person can't walk right in and expect to displace sites that were on the web and working to gain visibility ten, even twenty years before your first upload.  That's the situation when you arrive late to the battle. Just as a comparison.  If I upload an article on a twenty-year old domain with a DA of about 78 and a keyword of similar difficulty, that article might not rank in the top 100 for months, and might not rise to the first page for a year or more.  The people on the first page for your keyword are making money and will fight to hold it.

Thanks fellas for the replies. After a week and a half the rankigns came back and we actually moved up one spot. Essentially i removed 301's that were very old and were giving google 3 jumps to the new page (meaning there were mulitple old pages that redirected in order of history to the newest one). I also 301d all the old pages to the new page. We also re-enabled a page that was the parent directory of this page (this page linked to the page in question)and had about 150 links (orignally 301d to another page). Thanks

Thanks so much Don.  That was an excellent reply.  I really appreciate it.

Hi Justin, Sorry for the late reply here. Yes, I likely would do that. As long as the site categories are set up properly, you shouldn't require any product attribute pages to make a product discoverable for Googlebot. And the pa_ attribute pages tend to make for a poor landing page experience. If a product/attribute combination is especially important or profitable, I'd usually set up a custom landing page for that, rather than rely on the product attribute archive pages.

Thanks, this makes sense!

Is you current commenting system allowing FB logins? Because in my experience what users like about FB commenting is just the ability of commenting without first need to signup. I would stick with your current commenting system and just allow social logins, if you don't have already.

This is the right answer minus a few excess characters. If the blog structure is domain.com/2015/09/title-of-blog then the correct code would be as follows: RewriteEngine On RewriteBase / RewriteRule ^[0-9]+/[0-9]+/(.*)$ blog/$1 [R=301,L] This will result in: domain.com/blog/title-of-blog. In other words, Peter you had it right but you just had a few extra characters (you assumed the specific day was also included in the URL structure). Yours would work perfectly if the URL structure was domain.com/2015/09/02/title-of-blog Also, if anyone ever wants to test your rewrite rules this is a great tool. http://htaccess.mwl.be/.

Should I still try to rank my page even though the image is ranking as the first image displayed in the google results. Absolutely YES.  I have lots of first image in the SERPs and first listing in the organics.  Both of these bring traffic.  That traffic is generally not as valuable as traffic from organic web search but you can still make money from it.  (Visitors to Google image search are given the option to view your image or visit your page.  Sometimes when they view your image that viewing is done on Google's website, sometimes the visitor is moved to your website.  Google is known sometimes to frame your website within Google image search.  Google changes how image search works from time to time and some of their configurations produce almost no traffic for the owner of the image.) Will this count against me by Google if I do? Absolutely NOT.   It may actually increase your opportunities.  You then have great content from web search and great content from image search.  They should want to show that page to everyone! Or should I try to make the image being ranked more enticing for google searchers to try to increase traffic? Absolutely NOT.   Get two images on that page and attack with both.  Three would be better.  Four or five, better still. As in other things, much of this depends upon how much time you have to spend on it, how valuable the traffic might be and whether you are reaching for the competitor's throat or farting around. 

I saw a new page cached on Google, so it seems like Google was able to find some, if not all, new content, sitemap or not. What concerned me though, was the cached page had old meta data in it. That's what made me think that Google might have been able to find a sitemap on the website server, but the sitemap could have been pointing to the test (versus production) domain. I've seen that happen before. So it's good you submitted a new sitemap via Search Console. I'd also take a look a see if there might be conflicting sitemaps on the server.

You should 302 redirect non-authenticated users to http://twiends.com/login. This is a better user experience, and you avoid the potential authentication issues with the 301. It's also not really correct or useful to make it a 301 redirect: users aren't being 'permanently' redirected to the login page, and there's not much utility in forcing link juice to be passed from /settings to /login either. So requests to /settings should either show that user's settings or 302 redirect to /login. Don't duplicate the home page content and rely on a canonical tag. Your domain (and domain authority) are still going to benefit, and I just don't think there's enough of a case to sculpt the flow of link juice in this way. As Andreas has pointed out, the link juice isn't the most important consideration here; it's better to focus on user experience. Your homepage's ability to rank for any given term is unlikely to be affected by the decision to 'rel=canonical' all private pages to the home page.

Thank you so much!

Hi John! Did Don's response help? I have to say, I'm also curious as to why it's necessary to have 7 variations of these pages.

I've been spending time fighting other fires since posting this question. Yesterday when WP automatically updated it crashed my site.  I determined it was related to woo commerce...not good since most of my site is in the product categories & product pages of woo.  I spent all night an today on it and got my site working.  I read this forum which helped a lot https://wordpress.org/support/topic/wordpress-https-conflicts-with-woocommerce?replies=4 When I turned off the force SSL button the site came back online. In working with dream host support I learned this I'm the WP expert!  We've heard rumblings of a strange issue in Woo where that setting is forcing http redirects outside of the checkout page, which is causing Woo and core WP to send you back and forth between http and https when the siteurl is set to https. _Since https://www.cheaptubes.com is set for your home AND site urls, there shouldn't need to be a force of SSL. That is, WordPress already knows it's SSL, and therefore you shouldn't need to be forcing it on those pages. _ I then received  new crawl from Moz saying I now only have 9 errors, not 600. I am recrawling to verify its fixed but I think it is now.  If anyone else ever has this issue, try unchecking the Force SSL button

Thanks for the clarification EGOL, very useful! For other users, here's the link to hidden text EGOL is talking about.

You shouldn't use the nofollow tag property for internal links. Doing so used to preserve your PageRank, but it was changed a few years ago so that links with nofollow just result in link juice evaporation. But to answer your original question, the nofollow tags should have no impact on your blog. But do yourself a favor and remove the nofollow tags.