Google meta description uses <noscript> instead of js content - seo

On our page we have a <noscript> inside the <body> at top and via javascript we define the title and meta description of the page, as we want it to be dynamic.
However, on google search results the page appears with a random title of the page content and the description shows with the <noscript> content which is basically a message saying to activate javascript.
How can this be resolved? Is a static meta description required?
Thanks in advance for any input.

Related

Can I put Open Graph tags out of the head tag of my page?

I am talking about the Open Graph tag here. Can I put the og meta tag anywhere on the page?
I want to use my detail page image for the og tag, the easiest solution is putting the og:image tag in the body of my page.
Open Graph meta tags should always be nested between <head> tags.
To turn your web pages into graph objects, you need to add basic
metadata to your page. We've based the initial version of the protocol
on RDFa which means that you'll place additional <meta> tags in the
<head> of your web page.
http://ogp.me/#metadata
Additionally, keep in mind that order of the tags matters, especially when dealing with array tags (which includes og:image).
Open Graph Tag should be always always be placed on header tag until knowledge goes.. People please correct me if I am wrong..

Can meta tag description be declared dynamically in a web page

I have a dynamic page, where the contents and title will change based on the parameters in the URL. I want the same to be done for meta tag description. As I don't have a sound knowledge of SEO, I don't know whether it will be valid or not.
Say suppose URL contains word "test"
I will do,
if("test" is present)
{
<title>test</test>
<meta decription="test"/>
}
else
{
<title>test1</test>
<meta decription="test1"/>
}
Can I do this? Does giving two meta tag descriptions for same page work.
It is best practice to have different, on the page content based values of the title element and the meta description for each web page. It is not forbidden by the the HTML5 specification to have multiple <meta name="description" content="YOUR DESCRIPTION"> elements but I would guess that search engines process only the first appearance of the element. So my recommendation would be use one <meta name="description" content="YOUR DESCRIPTION"> element for each page.
As long as you code it server-side (eg in PHP) when the page is generated rather than client-side (javascript) after the page has loaded, then it will be fine. That's how most CMS systems work already.
Done server-side, only one of the description tags will actually appear in the code Google see.
Done client-side, it is likely that they will see no description at all as I don't think many search engines render javascript.

How prevent indexing of contents of a page, not the page itself?

How can I make front-page and category pages of my CMS being indexed just by their meta description tag not by their contents (posts, navigation, ...)?
edit: Contents on these pages are generated dynamically and change frequently, so I want to prevent users don't find what they saw in search result summary
edit: Can nosnippet help for this or does it prevent the display of meta description content too?
Also How I can prevent indexing of contents of particular tag in a page?
Add this between your head tags:
<meta name="robots" content="noindex,nofollow"/>
But, Yandex does not care about this which is not respectful.

Google +1 Generated Thumbmail in Profile

When you press the google +1 button on a site it grabs the typical meta data such as title and description. I thought it might be looking for the first image in the first article tag, but I tried changing the image and the thumbnail did not change. Does anyone know how the thumbnail is generated? Can it be added as meta info (similar to facebook likes)? Can it be linted?
The thumbnail i'm talking about:
There aren't any tools for developers on google+ yet.
You can subscribe for developer news
https://services.google.com/fb/forms/plusdevelopers/
API is available now
http://www.google.com/intl/en/webmasters/+1/button/index.html
<!-- Update your html tag to include the itemscope and itemtype attributes -->
<html itemscope itemtype="http://schema.org/LocalBusiness">
<!-- Add the following three tags inside head -->
<meta itemprop="name" content="title of your content">
<meta itemprop="description" content="description">
<meta itemprop="image" content="image url">
So... by the looks of it Google doesn't use the Open Graph Protocol http://ogp.me/ as their default information scrape.
For the image on the +1 listing they take the first useable image. The important part here is that even though on the +1 listing the image is resized to 45px x 45px the image you want to be used must be over 125px (at least). I'm using an image 180px x 180px (nice for scaling down to 45 x 45) and making sure it's the first large image on the page.
The title comes from the first h1 on the page and the description seems to come from the first paragraph; about 135 characters....
meta og:image works, secret is to have image large enough. It failed at 140x112 and work when I change to bigger thumbnail 511x364
Go to http://www.google.com/intl/en/webmasters/+1/button/index.html
Make sure to set "HTML 5 valid syntax" if you are using HTML5. I got it to work.

Will <noscript> hide the rest of the static content to Google crawlers?

This should be an easy one for someone:
Will the <noscript> element cause the HTML page to serve only the content within the <noscript> tag itself to google crawlers and hide all the rest of my static content causing it so not to be indexed?
Thanks!
No. The crawlers will see all your content, both within the <noscript> element and everywhere else.
Crawlers behave a lot like browsers with JavaScript turned off - they see all the static content plus the <noscript> content, but not anything JavaScript-dependent.
The whole HTML file is served in response to a GET request. Google should honour robots.txt and not spider directories marked with that.