Welcome to the Q&A Forum
Browse the forum for helpful insights and fresh discussions about all things SEO.
Either specified example is fine and one won't rank better than the other based on the domain on it's own.
Is your actual company called Electric Scooters 4 Less though? I would recommend a branded domain name in an ideal world, not having the keywords in your domain name is not going to hinder the rankability of the pages providing the content is quality.
This could potentially cause your website to suffer but it's all about ratio and balance. If the majority of your website's link profile is made up of these types of links, then it would be a good time to build some natural links to counterweight the existing ones.
As long as the positive metrics outweigh the negatives, generally, you should be fine. Just building some links with varying anchor text to the same page should ensure that you're website doesn't get hit further down the line by one of Google's black and white zoo animals.
Rich Snippet Markup should be implemented on the page containing the information not on links pointing to the pages.
Difficult to really advise on which approach would be best because from what I can gather, it doesn't sound like you're implementing the markup correctly.
Better to mark up the content on the location pages themselves with the address, locality, city/town etc as per my example above.
Might be worth reading up on exactly how Schema data works.
Just block /premium-content from your robots.txt page then (or include a meta noindex on the page if you can). There's no reason for it to be indexed I presume if it only redirects to your registration page and can't be access without authentication?
Disallow: /premium-content/
Hi Bill,
I did just type out a long response to you but it got lost when I posted the message, I think because the message I was replying to was deleted as a duplicate.
In short though, I described how the current template is better from a design perspective but all the issues are still apparent though. I checked out a product page form a 3dCart demo store and the issues are there too. The software is not open source either so unfortunately you're limited with their poor design / development whilst you host your store with them - just one of the many issues with hosted ecommerce solutions.
All you can really do is ensure page copy is clean, tidy and optimised along with ensuring page titles are unique, descriptive and optimised (required on the page in question).
We're actually building an RC Model ecommerce shop for a new client in the UK from within the next month or so if you would be interested in checking it out when it goes live.
The design of the website / product pages are poor and would be unlikely to convert well due to the layout and presentation of the information.
Just a redesign of the page would make a significant improvement to onsite behaviour I would expect.
A few points include:-
Conversions
Optimisation
Competition
Analytics
Have you analysed the data you have to learn:-
Overall, the website doesn't install trust in the consumer, this on it's own, won't necessarily produce a non-converting website but coupled with various other onsite factors, it's not going to prove overly successful.
Often, many ecommerce stores make very initial poor choices choosing poor ecommerce providers / solutions and this can lead to more design/development and conversion optimisation / SEO later down the line.
Hopefully that has been of some help to you though.
Is the problem that you have old URL's still indexed in Google or that Google Webmaster Tools is just displaying / accessing your old sitemap?
Let me know if none of the above answers your question.
What exactly are you trying to achieve? No rich snippet markup from schema.org is required to embed a testimonial into a page. If you are intending to provide additional information to a search engine which helps gather a better understanding of what your website is and does so they can display markup in the search results, then this would be where you would use the appropriate markup.
You may want to research the rich snippet markup for reviews to see if this is appropriate for what you're trying to achieve. It may be useful to read my other response to a schema related question I wrote a few moments ago too.
What are you trying to achieve? Do you have a page per location on your webstite and on each, this is where you're implementing geo/location based schema?
Which is better depends on its purpose, schema markup is intended to provide as much information to search engines as possible, anything of relevance to a website's products or services.
It is likely what you're after is the organisation markup, this can also appear in Google Places listings too. Look at the Microdata link at the bottom of that page and implement what is relevant to your website from there.
Currently rich snippet markup won't have a direct influence on rankings, however the correct implementation will make results from your website appear more prominent in search results.
It would be worth looking over the specification for Schema's organisation / local business markup too so you can see what is available to you.
Something such as the following should be relevant to what you are trying to achieve...
Business Name
Address Line 1
Address Line 2
City / Town
County / State
Post / Zip Code
777 888 999
Anything that you require testing to see if it is implemented correctly and will appear in the search results as you intend can be done with Google's Rich Snippet Testing Tool or this Microdata Tool.
Hope that points you in the right direction for now.
You'll have to rewrite the URL's rather than just remove reference to the path generally unless your CMS can cater for the required alterations.
Yes, you will, but it's going to prove far less of a headache than working with what you've got.
if you stick to the same design, import the same data, and keep the URL's the same; You won't hardly lose any page weight and authority.
Looking at the URL structure at http://www.nextgenrestoration.com/, the URL's can be kept the same with the right permalink structure.
If you're referring to the /blog content regarding everything having to be 301 redirected, then there will be a few simple processes available to make the migration smooth but seeing as this will be Wordpress to Wordpress database, you may as well export the old /blog and reimport the blog data before working on the new fresh install of Wordpress.
Hi Todd,
If the blog contained valuable content but was instructed to 301 redirect to a new location, then you are correct, the crawl would not go as far as crawling the content and subsequently indexing/caching or analysing value therefore any weight the actual content possesses will not transfer via the redirect however domain/page/URL authority / link juice / PageRank and other link metrics will, not 100% of this, but most of it.
301 redirecting is not designed to directly improve rank although other benefits of 301 redirecting can lead to this. Such as usability, traffic, relevancy.
Where are your questions? I'll take a look and see if I can help.
Was the homepage one of the pages that included the noindex meta tag?
Even if it was, pages will not all be crawled at the same time or in a particular order. The homepage may have already been crawled before the change was made on your site, your homepage may not have even be crawled at all today if it was visited yesterday for example.
Crawling results can vary hugely based on a number of factors.
The scenario you describe...
"I started eight blogs on a different host with keyword rich domain names to get some links to the shop. Today I don't update them, but they have a lot of links to our shop and the blogs have something like DA 20 and PA 30-40. There are lots of links between the blogs as well."
...is likely to match much of the criteria Google are using to hit sites with Panda / Penguin updates, to be honest, unless the blog content is of high unique content and not 'over optimised', I would not make any efforts to associate yourself with the network of blogs as it will likely do more harm than good over the forthcoming 12 months.
Really, you need to be assessing the overall value of each blog and whether similar content on your current webshop is a good match for the content on each of the blogs. If you're just contemplating 301 redirecting to improve ranking of keywords, then it's unlikely that this will be the result.
Sounds like a bit of a mess, if it were me, I would just do a fresh install of Wordpress, build a Wordpress theme improving their existing design, add the blog at the /blog location and have the whole website all using the same Wordpress install. Then 301 redirect any old URL's to new URL destinations.
Alternatively, just move the /blog content to a temp directory, then add /blog from the root instance of the Wordpress installation and then reimport the blog content from the MySQL database of the first instance (original /blog) of Wordpress.
Yes because that is what caused them to take notice of the meta noindex and drop your pages from their search results.
Best of luck with it, feel free to send me a PM if your pages haven't reappeared in Google's search engine over the next few days.
Hi Gary,
If the pages dropped from Google's index that quickly, then chances are, they will be back again almost as quick. If your website has an XML sitemap, you could try pinging this to the search engines to alert them to revisit your site as soon as possible again.
It's bad luck that the meta tag was inserted and this caused immediate negative effects, but it will be recoverable, and likely your pages should re-enter the index at the same positions as they were prior to today.
The key is to just bring Google's bot back to your website as soon as possible to recrawl, publishing a blog post could do this, creating a backlink from a high traffic site (a forum is a good example for this) are some methods of encouraging this.
Hope that helps.
How can Google Webmaster Tools be reporting duplicate title issues for pages that can only be accessed if you are logged in? If pages of your website require authentication then they are inaccessible to search engines so subsequently, cannot be reported on.
Unless I have misunderstood?