My site is handwritten to be lightweight in amp. It has two language alternatives, en and tr.
barakudabodrum.com/tr/ is in Turkish and should be targeting users in Turkey.
barakudabodrum.com is in English and should be targeting the rest of the world.
I am using rel="alternate" tags inside each webpage and not in sitemap.
My questions are not about SEO. At this moment I just want to setup correctly.
Should I create two properties for each language inside search console?
Should I have two sitemaps and two sitemap indexes?
Should I also mention about them inside robots.txt?
I found information pieces everywhere but not a complete guidance on different ways of international targeting.
Thanks
You mention that your question "is not about SEO", however, most of what you have asked does not make sense outside the context of SEO. The entire point of setting up something like an hreflang tag is to avoid algorithmic penalties for duplicate content and to optimize your organic traffic in terms of international SEO.
If you are not concerned about SEO, you don't have to worry about any of the questions you mentioned. If on the other hand, your questions are entirely about SEO, then here is what you should keep in mind.
From a Google Search Console point of view, you'll likely want to keep everything under a single account, as you have opted to use a single domain. If, on the other hand, you had opted for two ccTLDs, then you'd want to break things out under two separate Search Console accounts.
Looking at the way you have set up your hreflang tags, there seem to be some issues.
Take for example the tags from the following page:
http://barakudabodrum.com/en/diving
<link hreflang="x-default" href="http://barakudabodrum.com/dalis" rel="alternate">
<link hreflang="tr" href="http://barakudabodrum.com/tr/dalis" rel="alternate">
<link hreflang="en" href="http://barakudabodrum.com/en/diving" rel="alternate">
In the first tag, you have the hreflang set to "x-default", which is not a language code. At the end of this tag you have listed rel="alternate", an hreflang tag can have a rel attribute of either x-default or alternate, it cannot be both.
The best practices, for maximizing international SEO state that you should ideally have a sitemap for every language you target, as well as one for each country. Which leads me to a follow-up question, which is why you are not using country codes inside your hreflang tags.
If you where targeting only people in Turkey, who spoke either English or Turkish, you would use:
<link hreflang="tr-tr" href="http://barakudabodrum.com/tr/dalis" rel="x-default">
<link hreflang="en-tr" href="http://barakudabodrum.com/en/diving" rel="alternate">
If alternatively, you were targeting only English speakers from the United States and Turkish speakers from Turkey, then it would be:
<link hreflang="tr-tr" href="http://barakudabodrum.com/tr/dalis" rel="x-default">
<link hreflang="en-us" href="http://barakudabodrum.com/en/diving" rel="alternate">
Related
Generally, when I open the source page, basic thing when I see on my CSS or JS link rel is like below:
<link rel="stylesheet/less" type="text/css" href="http://blog.zakariyasoewardi.co.uk/wp-content/themes/wordpress-bootstrap/less/bootstrap.less">
I use third party plugin who claim can make nobody know I use WP, I'm sure my link rel will be like below if I setting with that:
<link rel="stylesheet/less" type="text/css" href="http://blog.zakariyasoewardi.co.uk/node/1/wordpress-bootstrap/less/bootstrap.less">
But in specific case, I need hack URL link rel much easier when people or I shot the source page, this is what I mean:
<link rel="stylesheet/less" type="text/css" href="/wordpress-bootstrap/less/bootstrap.less">
Is it possible?
I believe several developer can, I notice few of Website where I included in their service as member does well.
There are already answers for what you want to do:
https://stackoverflow.com/search?q=hide+wordpress
and
https://wordpress.stackexchange.com/search?q=hide+wordpress
and on the web in general
http://www.google.com/search?q=hide+wordpress
That said, this is called security through obscurity, which really isn't security at all. Bots will still find the fact that you are using WordPress. Casual viewers of browser source will, too. You're basically wasting your time.
You're much better off leaving all that alone and reading http://codex.wordpress.org/Hardening_WordPress and being sure you're on a good, secure web host.
WordPress isn't necessarily or chronically insecure (though, like any software package, vulnerabilities keep popping up). The main issue is that WordPress is very popular - 50 million sites and counting, they say, at the time of this post - and that makes it a target in terms of lots of insecure themes, plugins and sketchy hosts that cater to the WordPress ecosystem. And that means lots of targets in terms of millions of sites that may be mis-configured in terms of security.
I've been using the double-slashed, protocol-independent, version of URLs systematically whenever I can for a while now, in HTML (for href on anchors and src on images) and in JS (for XHR). Today I have been wondering if this would be possible on OpenGraph tags.
Currently I have this:
<meta property="og:image" content="http://static.example.com/image.png">
<meta property="og:url" content="http://example.com">
I have been wondering what the effect of using the following would be:
<meta property="og:image" content="//static.example.com/image.png">
<meta property="og:url" content="//example.com">
Is this allowed by the spec?
Is this allowed by (major) implementations?
Are there any obvious issues I'm not seeing?
Am I thinking about this completely wrong?
Has anyone done this or tried this before?
Okay, that's a bit too many questions, but you can see where I'm going: should I (and other developers who might chance upon this) use explicit protocols or is it okay to leave them off for og:* properties?
By adding these meta elements with the property attribute to your page, you are using RDFa (which is a serialization format of RDF). So you are participating in the Semantic Web.
The fundamental idea of the Semantic Web is using URIs to describe things represented by URIs. Some URIs represent web pages (we all know these), while other URIs represent real world or abstract things (like the person J. R. R. Tolkien, the concept of love, or the Eiffel Tower). (See this answer on how you could distinguish these.)
For example, this URI represents the physical world building (not a web page about that building):
http://dbpedia.org/resource/Eiffel_Tower
The HTTPS variant (https://dbpedia.org/resource/Eiffel_Tower) would be a totally different URI, which could, in principle, be used for something unrelated like a football or so. For RDF (in contrast to the common practice in the Web), there is no relation between a HTTP URI and its HTTPS counterpart.
So when you provide RDF statements about both URIs, it’s (at first) not clear that both are referring to the same thing. When you use an unique object for both URIs, then these could be mapped to mean the same thing. You can also explicitly specify with OWL (→ owl:sameAs) that two URIs are representing the same thing.
So, it’s not forbidden or wrong, but I’d advise to use only one of your "synonymous" URIs for a page/thing. Other people may want to make RDF statements with your URIs (→ things/pages), so it’s better that they all use the same ones.
No, it's wrong.
Why?
Facebook parser don't know how protocol use on site.
I am currently working on a project where I will have some pages translated entirely (meta-information on the project) and some pages (articles) only in one language, but still with the interface in many languages.
How should I handle this with regard to Google etc.?
I want the information to be available in all languages, so that people can find it with search terms in their local language, but can I get duplicate content problems if the articles are available on /fr/my-nice-article /de/my-nice-article with the same article text (not translated) and only translated interface ("Ecris un commentaire", "Schreibe einen Kommentar").
AFAIK Google automatically determines what language your content is written in. It users the language of the majority of all text. If you want to explicitly specify it, you can use the following snippet:
<meta name="language" content="de" />
Google, of course, shows only the pages in the user's language (so German Google users only see the de-content).
Found something directly from Google
Websites that provide content for different regions and in different
languages sometimes create content that is the same or similar but
available on different URLs. This is generally not a problem as long
as the content is for different users in different countries. While we
strongly recommend that you provide unique content for each different
group of users, we understand that this may not always be possible.
There is generally no need to "hide" the duplicates by disallowing
crawling in a robots.txt file or by using a "noindex" robots meta tag.
However, if you're providing the same content to the same users on
different URLs (for instance, if both example.de/ and example.com/de/
show German language content for users in Germany), you should pick a
preferred version and redirect (or use the rel=canonical link element)
appropriately.
I wrote a trivia game in Flex (flash). The site is written entirely in Flex. Almost all of the text is pulled from a database. It also has a fair number of images. The image file paths are pulled from the db.
My site's not getting any hits. If I check on google site:mysite it the url appears only. I know that inbound links are important and I'll try to get some. At the moment, I don't have any inbound links. In google webmaster tools, if I look under the site's keywords, there are 0. My sites been up for about a month.
Any suggestions on how to improve this situation?
(I've seen a few people ask for help with Flash SEO and the comments tended to be of the "don't use Flash" variety-- which aren't too helpful if you've written something in Flex/Flash).
Thank you.
-Laxmidi
Check out this article: Read Here
SEO FLASH PROGRAMMING
My recommended Flash SEO method uses a
DIV with search-engine-accessible,
primary content, and an open source
Javascript function called swfobject()
to detect when browsers are capable of
viewing Flash. When an appropriate
version of Flash player is present,
the Javascript manipulates the page's
document object model (DOM) to replace
the primary content with the Flash
movie. Most search engine spiders
can't handle Flash, so they will elect
to view the primary content. The
primary content may contain links,
headings, styled text, images—anything
we can add to an ordinary HTML page.
With SEO copyediting and coding skills
applied to the primary content, Flash
becomes a non-issue.
Flash accessibility programming isn't
spamming, as long as the primary
content and the visible movie are
essentially the same. The World Wide
Web Consortium (W3C) Web Accessibility
Initiative (WAI) specifically states
that multimedia content should have an
alternative representation available.
Accessibility programming creates the
benefit of presenting visual
information without losing the
visitors and search engines who depend
upon textual content.
As of July 2007, I discussed this
method with Dan Crow of Google. He
warned that this programming method
could draw attention because of the
possibility for abuse. If you use this
method, make sure the alternative
content is a faithful representation
of the Flash content, and avoid
combining this with other coding
methods that could be abused. While
this SEO method is not abusive, it is
aggressive because there is a small
risk that the search engines could
mistakenly decide that the primary
content is a form of cloaking.
I would also create a sitemap and link to multiple keyword rich landing pages about your game with a link back to the game. The more content google has to bite into the better changes someone will find you.
You also need to market your site...just because you build it doesn't mean they will come. Use twitter, facebook and any other form of social media to get the word out. You may also try buying a few bucks worth of ad words to start the ball rolling.
The solution to only the url appearing in Google is probably as simple as adding a meta description tag.
http://www.google.com/support/webmasters/bin/answer.py?answer=79812
http://googlewebmastercentral.blogspot.com/2007/09/improve-snippets-with-meta-description.html
It would also probably be beneficial to provide a description or instructions for the trivia game in HTML alongside the Flex part of the website, if this is possible.
Simply wondering if any SEO specialists out there know if Google or other search providers index meta differently because of the id generated by asp.net
Generally no, they will ignore meta tags and do whatever they please.
As stevemegson notes, the description meta tag is useful for providing your own description to display on the SERP (no guarantees it will be used).
Heres a great quote from the Wiki page for Meta_Tag:
Major search engine robots are more
likely to quantify such extant factors
as the volume of incoming links from
related websites, quantity and quality
of content, technical precision of
source code, spelling, functional v.
broken hyperlinks, volume and
consistency of searches and/or viewer
traffic, time within website, page
views, revisits, click-throughs,
technical user-features, uniqueness,
redundancy, relevance, advertising
revenue yield, freshness, geography,
language and other intrinsic
characteristics.