I've been using this URL extensively but now it appears to redirect to another page which doesn't contain the pertinent information
This is the link in question:
https://learn.microsoft.com/en-us/vsts/extend/develop/call-rest-api?view=vsts
But this is where it now takes you
https://learn.microsoft.com/en-gb/vsts/extend/reference/client/core-sdk?view=vsts
Where has the full reference gone???
Related
I have a website that has been replaced by another website with a different domain name.
In Google search, I am able to find links to the pages on the old site, and I hope they will not show up in future Google search.
Here is what I did, but I am not sure whether it is correct or enough.
Access to any page on the old website will be immediately redirected to the homepage of the new website. There is no one-to-one page mapping between the two sites. Here is the code for the redirect on the old website:
<meta http-equiv="refresh" content="0;url=http://example.com" >
I went to Google Webmasters site. For the old website, I went to Fetch as Google, clicked "Fetch and Render" and "Reindex".
Really appreciate any input.
A few things you'll want to do here:
You need to use permanent server redirects, not meta refresh. Also I suggest you do provide one-to-one page mapping. It's a better user experience, and large numbers of redirects to root are often interpreted as soft 404s. Consult Google's guide to site migrations for more details.
Rather than Fetch & Render, use Google Search Console's (Webmaster Tools) Change of Address tool. Bing have a similar tool.
A common mistake is blocking crawler access to an retired site. That has the opposite of the intended effect: old URLs need to be accessible to search engines for the redirects to be "seen".
I just signed up for a disqus account to set it up on my website.
I registered my website URL as http://www.mydomain.com
The place that I'm implementing the commenting system is in
'/article/:post_id'
example: http://mydomain.com/article/261
In each different article ID page, I want the disqus commenting system to show. I'm currently able to post a comment, but they're not displaying when I come back to the page. They are saved as part of the overall website which I see in my disqus admin panel but they're not showing on that particular article page.
Where do I set up the URL to make this work correctly?
I solved it by using a disqus_identifier
I have a strange problem in one Joomla website.
If i access from homepage and then navigate into the site it works correct, but if i go in some internal page from google results it shows uncorrect page layout, because the url is not correct.
This is the correct url
Correct page from homepage
and this the uncorrect url that Google finds Uncorrect page from Google
in this second page is showed rating module (that i never used) instead of an article, as you can see in links.
Someone can help me?
EDIT: I'm using Joomla 2.5 version. Every menu item is category blog type, and must show all articles of one category. Each category have 2 articles. In the uncorrect link seems that it access to single article, adding the rating that i have hidden in each article
Which version are you using?
if you can turn on SEF option in the global settings in joomla admin. Then you need to make sure all your articles are in menus. then if you link them on different pages it should keep the url the same.
The way you have it at the moment with all the x=123&... get params pages will show for what ever ids you change the menu to.
The reason you are seeing an uncorrect layout is the two different Itemid parameters (the right url has 127 while the wrong one has 104). The rest of the difference in the urls will be ignored by Joomla.
Solution: Find your menu item with id 104 (look at the menu ids on the right of the menu items view), then check which modules appear on the page from there. There may be modules in non-visible positions.
One of these modules is publishing the links with the wrong ids. If it's a Joomla core (like a search module) you can usually force the Itemid either in the module or in the component's configuration. Else you need to fixsome third party code.
Only once you have solved the multiple-itemid should you turn on SEF, otherwise you'd get the same problem only more difficult to trace.
sh404 could help you with this, I'd give it a try on a test site to see if it gets you out of trouble faster.
I made a Website for a client.
Now when I search for him the result looks like this:
You can see the fourth entry is somewhat of a special entry and I don't understand where this entry is coming from?
Is this an automated google+ page? I've just created a google places entry but never a google+ page.
How di I get rid of this search result?
Google Places entries show up in Google+ Local. They do not have a Google+ Page associated with them by default, but you can convert your entry to a place to enable more functionality and to hook the entry up with your site by using the badge code or the more minimal direct connect metadata link to verify your website on the Google+ Local page.
Associating your site with the Google+ Local page, should help with search too and provide people with a method to get directly to your site until the website starts showing up in the search index from being crawled.
I am creating an ios app that needs to download a html page and extract some information from it. To get to the page I also need to login. I have looked everywhere for some code on how to login to a site using the cocoa framework, but every answer I see only seems to answer half the question. Here is the login site: romres.ist-asp.com. I need some code for writing something in the first field (the other two are left blank), then submit the form and then I need to be able to see the next page. I believe apps like Facebook should use som of the same technology, where you log in to a facebook and then you can see the contents of your profile.
Basically what you want to do is called scraping.
Scraping is really easy for sites that don't require authentication, but in your case what you should do is to inspect the POST request being made when logging in the site your interested in (try to understand of the service respond) and the POST request made, when already logged in, to retrieve each page.
The purpose of all of this is to have later the possibility to simulate regular HTTP requests that should came from a browser via code.
If you have any doubt ask in the comments.