duplicate url+content generation problem - url

In my current site I have a link in the header section for skype, Gtalk, MSN chat, by clicking on the link the chat application get launched.
The problem is that, the link uses a href tag. and by doing this the SEO process is facing problem as there is some duplicate url have been created. In SEO process if different URLs have the same content the process not works.
Any suggestion from coming out from this problem.

One simple way to remedy this is add this adding a element with the attribute rel="canonical" to the section of the non-canonical version of the page.
More information please go to http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=139394

make them js url (with the js function in an external script)

Related

Wrong WordPress links redirection

I have a WordPress web site and the site links was working good. For the last two days, suddenly found web site links redirect to the home page not the target link page. I checked the links code it's okay. I inspect links in the browser and I found this code changed for all links like this :
اتصل بنا
This means the right link code in ohref property and the alternative link code in href so all links open the main page for domain in href property.
What is the solution and what caused this problem?
href="" is where the link is directing. ohref="" is a custom attr that can only work with a javascript function. So unless you have an on click listener with javascript it has no function.If there is a javascript function it will overwrite the href="" with a preventdefault()

Alert says using deprecated HREF without absolute URL

Message alert in Facebook developer page that my site is currently using the following deprecated features:
Social Plugins (Like Button, Like Box) without absolute URL's in their href parameter. This must be fixed before July 2013.
I'm guessing it's talking about the data-href parameter for likes, but my like buttons are being generated with the following simple code:
data-href="http://<?php echo $_SERVER["HTTP_HOST"].$_SERVER["REQUEST_URI"];?>"
And the results when viewed in the browser (looking at the HTML source) certainly look like absolute URLs to me. What is this alert actually trying to tell me? That they've scanned the site and that there are actual HREFs that have problems, or just that there might be some?
Is it referring to some other HREF parameter?
If you use absolute url in data-href attribute of this social plugin, just enable July 2013 Breaking Changes in settings of your facebook application.
In Like Button code, data-href is href for HTML5.
Absolute URL:
http://stackoverflow.com/questions/16270043/alert-says-using-deprecated-href-without-absolute-url
Relative URL
../questions/16270043/alert-says-using-deprecated-href-without-absolute-url
Social Plugins must have absolute URL your site and looks like your site has.

Breaking Change about absolute URL in Social Plugin

I got this alert from facebook:
... is currently using the following deprecated features:
Social Plugins (Like Button, Like Box) without absolute URL's in their href parameter.
The fb like and fb comment box is used on a Sharepoint site, and the URL in the href parameter is absolute.
Anyone have ideas why facebook is complaining about the code? or have a safe approach I can use to test if the code will work after the change without downtime on the plugins.
Just as #Anvesh says, I checked that my URLs was absolute, enabled the migration, waited a few minutes and tested and nothing breaked.
They should rephrase the message.

Something wrong with redirects on my Joomla 1.5.18 site

My Joomla 1.5.18 site, I enabled login, when I click login the page I get sent to is NOT styled with CSS. If I login it redirects to the home page and it is not styled anymore either.
It looks like it is recursively appending stuff to the URL incorrectly.
http://www.myjoomlasite.org/index.php/index.php/login
if I click on home page or login links it keeps putting more and more index.php entries in the URL, and sometimes on the end. The following is what I get when I try and go to a JEvents menu item.
http://www.myjoomlasite.org/index.php/index.php/index.php/index.php/upcomingevents/month.calendar/2010/06/09/index.php
Anyone have any idea why this is happening? I don't know what to search for on Google apparently, and none of the Joomla! books I have address this.
I figured it out I had turned on Search Engine Friendly URLs in SEO Settings under Global Configuration. Turning this back off fixed the problem. Now I guess another question will be along the lines on how to get the Search Engine Friendly URL's to work again.
Make sure you link to stylesheets and images using a link that starts with a leading slash and therefore counts from the root.
It is the browser that evaluates the URL for those resources, based on the URL of the currently viewed HTML page. Never use relative links for these resources.

Clicking relative link goes to about:<relative link> which does not show wanted page

I am using version 14.67.9 of TembeddedWB in a project in delphi 2007. I use TembeddedWB in combination with loadfromstring. That all works like I want it to but when clicking on a link in the page it goes to a page I am not expecting. If for instance the page is on a particular IMDB result site and one clicks on the link the browser goes to about:/title/tt1041829/. I guess I forgot to set some extra property or I am doing something else wrong. If somebody here can point me in the right way i would appreciate that.
It looks like the browser's current URL is not updated and the default "about:blank" is used. I guess this may happen when you don't navigate to the web site directly by Navigate or Navigate2 method but load the HTML from a local file or stream.
Edit: I see, you are using LoadFromString which confirms that.
In that case, it should be possible to use OnBeforeNavigate2 event to fix the URL.
The problem is that the web page you are accessing uses relative links and the reference point that it would be relative too is your loadfromstring which loads through the "about:blank" page. Another way of fixing this would be to inject a &LT;BASE href="http://www.originaldomain.com/originalpath"&GT; tag in the HTML header (between the &LT;HEAD&GT; and &LT;/HEAD&GT; tags) which points to the location the page was accessed from. This will tell the browser where relative tags start from and will fix the problem without requiring inspection of every link.

Resources