Welcome to the Q&A Forum
Browse the forum for helpful insights and fresh discussions about all things SEO.
ALT tags are for accessibility, not SEO. Screen readers will look at those tags and read to those that have trouble with seeing the page what the image is.
As long as the ALT tags are accurate representations of what the image is, you should be okay. If you are attempting to stuff keywords into ALT tags and they do not accurately describe what the image is, then you may not receive any benefit and could potentially get some kind of penalty.
If you are talking about the links you created in your profile, those are all "nofollow" so there won't be any value. To get one of them to be a "follow" link you have to earn a minimum of 200 MozPoints.
If you want to control your image in Social Media you need to include these tags, you don't need all of them if you are only interested in one platform
Once you have them on the page and filled out, you will need to tell Facebook or Twitter to update the markup with this tool
https://developers.facebook.com/tools/debug/
https://cards-dev.twitter.com/validator
| |
| | itemscope itemtype="http://schema.org/Article"> |
| | itemprop="name" content="Page Title"> |
| | itemprop="description" content="Page Description"> |
| | itemprop="image" content="Image URL"> |
| | |
| | |
| | name="twitter:card" content="summary_large_image"> |
| | name="twitter:site" content="@yourtwitterhandle"> |
| | name="twitter:title" content=""> |
| | name="twitter:description" content=""> |
| | name="twitter:creator" content="@"> |
| | |
| | name="twitter:image:src" content=""> |
| | |
| | |
| | property="og:title" content="" /> |
| | property="og:type" content="" /> |
| | property="og:url" content="" /> |
| | property="og:image" content="" /> |
| | property="og:description" content="" /> |
| | property="og:site_name" content="" /> |
| | |
| |
I've used URL profiler to for a content audit on our own site. It helped us to identify the areas of our site that needed to get cleaned up, and more importantly, which pages had thin content. It was also helpful when trying to prioritize which sections to do first.
Craig's article highlights another useful way to utilize the tool, looking forward to trying it out.
A couple of things come to mind:
Why don't you want the product pages to be in the index?
Why is there concern of a penalty?
As to your question:
* Do the URL's have parameters? If so you can set those in GWT and inform Google what they should do when they encounter them as they crawl the site.
*Canonical the pages you don't want in the index if possible to the static pages.
The underlying thing is that they are the few sites that are doing it, so in the absence of a better option, Google shows these sites instead. Think of ehow.com or ask.com, they don't provide a great experience to the user, but you will notice on those types of searches, there are not any better options out there.
When I say dynamic, I don't mean it as it is created on the fly. The URL has parameters that the server sees and knows to fetch the corresponding city from the server. I am not 100% positive, but from past experience I am willing to bet there is some kind of auto-fill tag like %CITY% that the server will plug in the city from the URL parameter. The rest of the copy never changes
Example: http://www.travelsite.com/flights-from-boston-to-new-york-bos-to-lga
Copy on page: blah blah blah Boston to New York blah blah blah. If you were to change either of the cities the copy would remain the same but the city would update.
Crawlers will crawl the page after it has loaded, so as long as the "dynamic" content is loaded prior to that the crawler doesn't know any different.
If my memory serves pages only need to be 5-10% different in copy to not be counted as duplicate content. So if your title, H1 and a few words in the sentence and some links are different that just about does it.
Now this doesn't make it a great user experience and as StreamMarket stated below, eventually Google will take notice of this and will move them down in ranking. Of course, this also means that other sites (Airlines) need to do a better job at creating pages like this but are user focused and not search engine focused.
Amen Amelia. I said the same, but not nearly as thorough as you did.
Have you done a Fetch as Google for the page? If I notice a page not getting picked up I do a fetch and render. This will tell you if there is something blocking Google from viewing the page.
Hi Rich,
If you have conversions set up you can see them in Real-Time or at least what GA considers it to be
In you GA dashboard click Real-Time > in that drop down towards the bottom there is Conversions. It will show Active Users that hit any of the goals that you have configured.
You can also see traffic sources, location of the visitor, any events set up and what pages they are viewing all in real time.
Being in the travel industry these are the same observations that I've noticed.
My theory behind a few of them:
For your second question, I know one online travel agency put in a lot of money and time to create dynamic style pages when searching for flights between city 1 and city 2. You can alter the URL by changing the airport code and city name and the copy within that page remains the same with the exception of the city names. There are companies as well that will build out the actual pages with any desired URL structure you would want.
Agree - but if you are concerned about any Google penalty from these links you can always disavow them.
I agree with Kevin, use what is common for those that are searching for the information, and think using both is a good idea. In my industry it is common to see both city and airport code in the URL
Example of what I commonly see:
http://www.kayak.com/flight-routes/United-States-US0/Seattle-Tacoma-Intl-SEA
http://www.kayak.com/flight-routes/Los-Angeles-LAX/Seattle-Tacoma-Intl-SEA
http://flights.expedia.com/flights-from-seattle-to-los-angeles-sea-to-lax/
When you create event tracking, you can assign a category and label to each button that would help classify the clicks for easier understanding of user behavior.
Here is the code that I use
| onclick="ga('send', 'event', 'Category', 'Action', 'Label');" |
So if I had a category for shoes, action is add to cart and the label would be the specific shoe like Orange Adidas F-30 the code would look like this
| onclick="ga('send', 'event', 'Shoes', 'Add to Cart', 'Orange Adidas F-30');" |
When you view Events in GA, you can then see all up overview, or broken down by category, or action if there is more than one action and then the specific item.
It's a lot of manual work, I use Excel to help with the code by using the Concatenate formula.
I would set up query parameters in GWT to tell Google to crawl and index those pages. This would allow for those pages to be indexed and hopefully drive traffic along with the main category pages.
https://support.google.com/webmasters/answer/6080548?hl=en&rd=1
If you have a mobile equivalent page to your desktop page, make sure to redirect your mobile users to that page. Make sure that you do not redirect all users to the m. homepage, that creates a poor customer experience which Matt Cutts has said will result in poor rankings for your mobile site.
Make sure you use the correct canonical tagging between the mobile and desktop pages. GWT talks about the correct use of these tags here https://developers.google.com/webmasters/smartphone-sites/details
First thought, where is the traffic coming from > organic, email, direct, etc.?
You can also view Search Analytics in console (GWT). I would view pages and select the time period of the spike, compare it to the previous period then view queries to see if there was a spike in impressions for any terms. Check positions and see if also during that time any term increased in rank. It could be with the recent algo updates that you've benefited from a higher position that has helped.
Subdomain is better than separate domain if you cannot have a subdirectory.
As for the duplicate content, regardless of a separate domain, subdomain, or subdirectory, I would canonical any of the duplicate pages to the authoritative content. If it's the main site, then I would canonical the other domain to it. Not sure of a reason why you would prefer the other domain to be the authoritative source, but if that is the case, then you would canonical the main site to the other domain.
Without knowing the URL it's hard to troubleshoot if there are technical issues with the page/site.
If you don't want to post personal or business stuff here no worries.
Things to try:
Screaming Frog - have it crawl your URL to find any issues
Do a Google site search to see if they have any pages indexed
Use semRush for those URL's and see if any keywords rank
Is GoDaddy your host or just the registrar? If they are not your host, contact them. Make sure to provide the exact error from GWT to help troubleshoot
Check robots.txt to ensure that isn't blocking.
Those are the few things top of head I would try
Very strange that you CPC data shows a much smaller increase than GA, especially since they are connected. Maybe a quick call to Google to see if maybe GA glitched during that period.
Here is the page for Google support, I would try the paid search avenue as that seems to get you better results when chatting with them. Just mention your AdWords data give a different story than GA and see what they can figure out.
https://support.google.com/adwords/answer/1385067
Good luck.
ht
tps://support.google.com/adwords/answer/1385067
Now that our entire site is HTTPS, there does not seem to be any negative impact to our URL's by leaving off the HTTP protocol. If there was any traffic lost, it didn't seem significant as our reports did not indicate a decline. One year later, traffic through SEO is higher than before we implemented.
I personally agree with Everett, don't leave things to chance. I did require that the homepage did have HTTPS for the canonical though. I felt massive panic attacks while we were going through the transition. However, if you are unable to convince your developers the importance of using an absolute path for canonical this did not seem to have a negative impact on our site.
I am glad that we didn't have any noticeable impact, but I am also glad that I didn't turn it into a bigger issue within our leadership team. Since we didn't see anything negative, it could've reduced my credibility within the business which would've had made it difficult for larger SEO problems.
BTW, we are still using relative canonical tags today. (except the homepage, that still has HTTPS)
This is a rather difficult question to provide a clear answer for. There is not one thing that will influence DA, rather several things done correctly over time may or may not influence your DA.
For more information, I strongly recommend reading this from Moz - https://moz.com/learn/seo/domain-authority
Your best bet would be to login to the WP account and have it redirect to your new site. This would be the quickest way to let Google know that the WP site is the old site, plus if you had any links to it the juice would flow to the new one instead of going away.