Wix Support: Create a page with wild card url - url

I have wix website. I do want to create a page with a custom url.
So briefly I want all the url with
www.somedomain.com/books/*
to be redirect to my created wix page.
Any way possible.
Url Example:
When ever user types url such as:
www.somedomain.com/books/1
www.somedomain.com/books/2
www.somedomain.com/books/3
www.somedomain.com/books/4
www.somedomain.com/books/5
www.somedomain.com/books/6
then the redirection should be to my created page on Wix whose url is: "www.somedomain.com/books"

Assuming you meant you have full control over www.somedomain.com/books/, you could redirect using HTML.
Go to the head tag --> add the code:
<meta http-equiv="refresh" content="0; url=YourWixSiteHere.com" />
if you want to make this shorter, I'm not sure how

Related

Should the url property in WebSite represent the main page or the current page being rendered?

I am trying to add Microdata into my site to help search engines understand my content. The WebSite definition requires a property called url. I am puzzled on which URL I should have here. Should the url be the URL to the main page or the current page being rendered?
For example, if I want to create Microdata for https://example.com/i/12/some-tag. Would the url then be https://example.com or the canonical URL (i.e., https://example.com/i/12/some-tag)?
The url of the WebSite should be the website’s homepage.
If you want to provide structured data about the current page, you can use WebPage and its url property.
<!-- on https://example.com/i/12/some-tag -->
<body itemscope itemtype="http://schema.org/WebPage">
<link itemprop="url" href="https://example.com/i/12/some-tag" />
<div itemprop="isPartOf" itemscope itemtype="https://schema.org/WebSite">
<link itemprop="url" href="https://example.com/" />
</div>
</body>
For the homepage itself, the WebSite and the WebPage would have the same url value. By giving each item its own URI as identifier (via Microdata’s itemid attribute), you can differentiate between these two (and all other) items. See this answer for details.

How do I claim a URL for Facebook Instant Articles

When I try to claim my URL I get this error:
The fb:pages tag on the url doesn't contain this page's id. The url has
fb:pages tag but they don't have this page's id. Please work with your
developers / webmaster to add this tag to your website.
Am I supposed to place this meta tag: <meta property="fb:pages" content="130810137587****" /> in the head of my web page's HTML before I can calm my URL? Or in the head of my Instant Article's HTML
?
You place that meta tag in the html for the url/subdomain/path you are trying to claim. Not in the instant articles.
If you're using Wordpress add your meta tag in the header.php file in the <HEAD>...</HEAD> section
You must put the tag between the tags of your website in the index
<Head>
     <Meta property = "fb: pages" content = "130810137587 ****" />
</ Head>
You probably also need to update the open graph 'type' property:
<meta property="og:type" content="website" />
As is said here:
https://www.facebook.com/business/help/community/question/?id=10156960334050657
Facebook is trying to read the metadata from your canonical URL, you can check which URL it's using on their debugging tool:
https://developers.facebook.com/tools/debug/
Paste your URL and check the Canonical URL info and its headers, that's the domain you need to update with the meta tag .
In my case, it was pointing to a different URL in my test environment.
Hope this helps
I have the same error.
you need to add the meta tag inside Head tag. of your website.

Show always canonical tag with mvc sitemap provider

i'm using the MVC Sitemap Provider 4 and want to show always the canonical tag, not only when a second link is existing. Is there somebody who can help me?
The best way to do this is to edit (or create another) template to build the canonical tag. If you installed using the NuGet package, in your /Views/Shared/DisplayTemplates folder you will have a CanonicalHelperModel.cshtml file (or with a .ascx extension if you are using webforms instead of razor). The default looks like this:
#model MvcSiteMapProvider.Web.Html.Models.CanonicalHelperModel
#using System.Web.Mvc.Html
#using MvcSiteMapProvider.Web.Html.Models
#if (!String.IsNullOrEmpty(Model.CurrentNode.CanonicalUrl)) {
<link rel="canonical" href="#Model.CurrentNode.CanonicalUrl" />
}
You can change it so it uses the URL property if no canonical URL was resolved by adding an else block.
#model MvcSiteMapProvider.Web.Html.Models.CanonicalHelperModel
#using System.Web.Mvc.Html
#using MvcSiteMapProvider.Web.Html.Models
#if (!String.IsNullOrEmpty(Model.CurrentNode.CanonicalUrl)) {
<link rel="canonical" href="#Model.CurrentNode.CanonicalUrl" />
} else {
<link rel="canonical" href="#string.Format("http://www.mysite.com{0}, Model.CurrentNode.Url)" />
}
You may need to devise a better way to get the base URL (domain name and http/https) and reliably concatenate it with the URL property, as the canonical tag requires an absolute URL. You could just grab the current Request.RawUrl instead of Model.CurrentNode.Url, but you will need to ensure it is properly sanitized (and HTML encoded) before displaying it on the page to prevent XSS attacks. However, if you use the Request.RawUrl just to get the base URL (by loading it into a Uri object and then using the base URL parts), you should be fine.
This will only work for pages that have a matching node defined in the SiteMap. If reading the nodes from an external source such as a database, you should ensure that each record in the database has a node in the SiteMap so there is a one-to-one correlation (at least for the pages you want indexed in search engines). You should not be using preservedRouteParameters in this case. For more information on that subject see How to Make MvcSiteMapProvider Remember a User's Position.
On a side note, there really is no need to do what you are asking because the only pages that require canonical tags are the duplicates.

Understanding og:url

I am working through the Facebook tutorial for iOS and am having trouble when a get to the final part with Publish Open Graph Story. I have gone through and set everything up as best I understand. When I try to test using the Object Debugger I get "Missing Required Property: The 'og:url' property is required, but not present." Can some one help me and explain this tag and how it should be set?
Thanks for the help.
Have a look at ogp.me they define og:url as :
og:url - The canonical URL of your object that will be used as its
permanent ID in the graph, e.g.,
"http://www.imdb.com/title/tt0117500/".
Basically as jeff sherlock of facebook explains in this post: https://stackoverflow.com/a/7831012/228741
That when you give the url of your action (the one containing meta tags) facebook ignores everything that is on that page (doesn't render it) . But it renders whatever you have given in the og:url.
What i do usually is have my og:url call the same page with the parameters. So facebook renders the same page for me. If you want to render some other page you give the link in the og:url.
This is set as a meta tag in the <head> section.
Example :
<meta property="og:url" content="your url">

Like button - using mod re-written friendly URL and none friendly URL for count value

My site has an FB like button on a dynamic page.
There are also mod re-write rules on the site to allow a friendly URL for that dynamic page.
i.e the following opages are the 'same':
(url 1) www.getawayearth.com/property.php?id=703
(url 2) www.getawayearth.com/property-rental/holidayhome703.html
The page has a like button on it.
My problem is that the like button shows different values for each url, even though the the page is the 'same'. For example if you were to visit URL 1 an click on the like button, the like count would not be registered URL 2.
I understand why this is happening, however I was wondering if it is possible to set the like button to recognise the both urls as being the same?
If you have multiple Like buttons which should all 'like' the same thing, you need to point the href of the like buttons to that URL - i.e on page 1 and page 2, both like buttons will be of the form <fb:like href="http://example.com/page1"/>
I understand your issue, and Open Graph meta tags could be a way to let Facebook now that 2 different URLs are the same by setting the same og::url meta on both each URL page.
The same issue occurs with SEO, and it's why there is a meta data named "canonical" to specify the official URL of a page, even if there is different URLs to reach the same page content.
<html>
<head>
<meta name="title" content="your page title" />
<link rel="canonical" href="http://your-official-page-URL" />
<meta property="og:title" content="your page title" />
<meta property="og:url" content="http://your-official-page-URL" />
</head>
…
Hope that can help.

Resources