I was wondering why Google adds a suffix to my website, but I don't know why just this specific word.
The website I am talking about has a sub domain. To keep this post free of ads, let's say the domain is:
http://sub.my-name.com/
So when I search for my website on Google I get this:
"Lorem ipsum| Specific Page Title - my_name"
Original page title:
<title>Lorem ipsum | Specific Page Title</title>
Maybe Google got this word from here, but why?:
At the bottom / footer of each website I include the following code:
<div class="container">
<p class="any-class"><b>my_name</b>
</p>
</div>
The main website http://my-name.com/ has the following code:
<div class="title">
<h1 class="title-text">my_name</h1>
<p class="title-sub"><b>this is</b>a subtitle</p>
</div>
and
<title>my_name</title>
Where and why did Google get this word from?
How can I change this suffix (if it is possible).
Thanks for your ideas, Jonas.
If you are using entirely different title tags for your pages, Google tries to add a common string. This is done to prevent title spamming.
For example if your /index.html has the title “Foobar - Welcome to the website“, Google may add “Foobar“ to all pages with short or disconnected titles.
Related
I want to link the logo of my site (in my main header) to the homepage of my store. I could do so by linking to the absolute URL (e.g., https://www.example.com), but that doesn't work when I'm testing on a development server that isn't hooked up to my domain name.
I know that I can link to pages using <a href="{{ pages.example.url }}">, where example is the page I want to link to. But using <a href="{{ pages.index.url }}"> doesn't seem to work — I'm assuming because index is not actually considered a page.
Is there an easy way to link to my store's homepage using a liquid tag?
You can use {{ shop.url }} as listed on this variable cheat sheet and in the Shopify developer reference.
Returns the full URL of a shop.
http://johns-apparel.com
Homepage
You also have the option of using the secure version {{ shop.secure_url }}
Returns the full URL of a shop prepended by the https protocol.
https://johns-apparel.com
Homepage
I also found in a quick test that it will also return the preview URL when previewing an unpublished page e.g. k29ijan0ye0r5g7k-51325174.shopifypreview.com
I figured it out, for those curious: Just link to "/". So, a link to the homepage of your site should appear as follows in your header.liquid file:
Link
Link This doesn't work for multilanguage stores.
I think better solution is: {{ routes.root_url }}
Is it possible to embed different Google+ comment boxes to a post that has different string ids in the url.
For example:
http://www.distressedvolatility.com/p/trending-news.html#3.18771?icx_id=http://www.voanews.com/a/janet-yellen-signals-interest-rate-increase-likely-this-month/3748729.html&showTitle=true
and
http://www.distressedvolatility.com/p/trending-news.html#3.13006?icx_id=28666&showTitle=true
Thanks.
The Google+ comment box shows the comments based on the URL, by default the URL is set via Blogger layout tag (like for example <data:post.canonicalUrl/>) so that the comments are linked to a single URL despite the post URL changing in the address bar (like mobile version appending ?m=1 or different ccTLDs Blogger uses). To render different comment boxes based on the URL, you can change the href parameter to window.location.href. The code for same will look like -
<script src='https://apis.google.com/js/plusone.js' />
<div id='comments'>
</div>
<script>
gapi.comments.render('comments', {
href: window.location.href,
width: '590',
first_party_property: 'BLOGGER',
view_type: 'FILTERED_POSTMOD'
});
</script>
I say I have a section of a page like this (rough HTML to give an idea):
www.mydomain.com/contact-us
<div class="regional-offices">
<div class="south-west">
South West
<div class="south-west-content">South west office address</div>
</div>
<div class="north-east">
North East
<div class="north-east-content">North east office address</div>
</div>
...
...
Currently, these are a set of accordions that expand to show the content when the link is clicked. What I would like to do is treat them as individual URLs so that they can be seperately indexed by Google, as of course at the moment they are just part of a single page.
I have been researching the History API and can see how I would do this as far as creating unique URLs for each section, but where my understanding falls down is how Google or other search engines will handle these links if the required info is already part of the page and not stored at its own seperate URL.
For instance, the first step would be to change the <a> tag to be something like:
North East
We can then use JS to preventDefault() going directly to the URL, and instead provide the user with an expanded accordion, bring the page scroll down to the accordion and a unique URL using the History API. This is all well and good if we visit the URL directly, or click any of the links.
But the problem is that as far as I know, the Google crawler will try to follow the link and be faced with a 404 because there's no Javascript preventing access to the resource in the URL. And nor do I want there to be.
Or is it the case that I will need a unique location holding the contents of the accordion, which is indexable, and also pulled in with AJAX when a collapsed accordion is interacted with?
Apologies if I haven't made anything clear.
I had to deal with the same thing. What I did was to make a rewrite rule so that the link that google follow is actually posted to the page that handle the the request. to display the data. Angular might save you a lot of trouble to dealing with accordions.
I have found this link:
Adding a Google Plus (one or share) link to an email newsletter
It's great, it helped me to make a Google+ button for my HTML Email campaign. I'm using Mailchimp and I edited it as such:
<a href="https://plus.google.com/share?url=*|RSSITEM:URL|*">
<img src="http://mywebsite.co.uk/images/googleplus.jpg">
</a>
So now it has a customised image, and also works in my RSS email campaign. Mailchimp support didn't know this was possible, so that made me happy.
HOWEVER, what I want to achieve is to be able to choose which image is shared by default when the user clicks. Does anyone know if that's possible?
I hope my solution helps someone :)
The image that is displayed in the share is determined by the Schema.org markup on the page that you are sharing. Specifically, you will want to set the itemprop="image" to point to the image you wish to share.
<body itemscope itemtype="http://schema.org/Product">
<h1 itemprop="name">Shiny Trinket</h1>
<img itemprop="image" src="{image-url}" />
<p itemprop="description">Shiny trinkets are shiny.</p>
</body>
It is important to note that this is the markup for your page, so the same image that appears in the share is the one that will represent your page in other snippet tools.
You can see how this works, and see additional markup options, at https://developers.google.com/+/web/snippet/.
the sharer uses this image as the default one, but displays other images as well (they can be selected with the arrows on hover). Is there a way to disable the other images, for navigation images etc.?
I have re-designed and deployed our commercial site using 100% Ember using pushState to increase the search engines capability to browse the site content.
But, I have one issue that I am not sure how to solve. I am using "actions" to redirect to Ember App routes.
As an example, here an "a" tag:
<a {{action "doSales"}} title="Sales and after sales services">Sales and after sales services</a>
The associated action:
doSales: function(router, event) {
router.transitionTo('sales');
},
And the route:
sales: Ember.Route.extend({
route: '/:locale/sales',
But, in the DOM, the final a tag will look like:
<a data-ember-action="9" title="Sales and after sales services">Sales and after sales services</a>
As you can see there's no href="/en/sales"
Which means that if I ask a browser to browse my site, it won't be able to dig down the site structure.
Does anyone knows
Action href support was removed with the new router.
If you want href's on your anchor tags, you will either need to move to using the {{#linkTo}} helper (which generates them automatically) or add in the href values manually.