Google SDTT error: "All values provided for http://www.example.com/ must have the same domain."

Question

When I copy/paste JSON-LD example from Google Documentation (code-snippet below) I get an error in the Structured Data Testing Tool:

http://www.your-company-site.com (All values provided for http://www.example.com/ must have the same domain.)

Why is Google's own documentation example giving an error?

Code snippet from Google’s documentation:

<script type="application/ld+json">
{
  "@context": "http://schema.org",
  "@type": "Organization",
  "url": "http://www.your-company-site.com",
  "contactPoint": [{
    "@type": "ContactPoint",
    "telephone": "+1-401-555-1212",
    "contactType": "customer service"
  }]
}
</script>

It's weird, the code didn't throw error message one month ago. — rj487, Nov 01 '16 at 06:57
A single line of documentation would make the tester way more usable! — Michael, Feb 13 '17 at 09:32
The answers and comments below seem to hold the correct info. Let's add an accepted answer and link all the other questions on this topic. — Michael, Feb 13 '17 at 09:45
Another FYI: apparently this "error" only pops up for Organization types; I don't get this error for a Website entity — Michael, Feb 13 '17 at 09:48

score 10 · Answer 1 · answered Jan 03 '17 at 14:40

10

It appears the testing tool assumes example.com as its domain.

When testing if you can update your url to "www.example.com" it will validate successfully.

<script type="application/ld+json">
{
  "@context": "http://schema.org",
  "@type": "Organization",
  "url": "http://www.example.com/",
  "contactPoint": [{
    "@type": "ContactPoint",
    "telephone": "+1-401-555-1212",
    "contactType": "customer service"
  }]
}
</script>

answered Jan 03 '17 at 14:40

sidarcy

2,958
2
36
37

1

I confirmed this. – TrueWill Jan 13 '17 at 15:33
Confirmed. Apparently just the main URL will do, which is double weird. – Michael Feb 13 '17 at 09:44
3

as in @Bryan Heckler answer it should be the domain of the page that the snippet is embedded in: "url": "https://search.google.com" – ivoba Apr 19 '17 at 07:44
It appears this is no longer true – Alex Jul 17 '17 at 19:24

score 5 · Answer 2 · answered Nov 02 '16 at 13:49

5

This error started appearing somewhere in the month before your post. Since the error disappears when the "contactPoint" is left out, even though it doesn't contain an URL, this is most likely a bug in the validation tool.

I came across the same problem and asked about it on the support forum.

answered Nov 02 '16 at 13:49

DieterDP

4,039
2
29
38

It appears that if you update the `@context` from `http://schema.org` to the same URL as your site, the 'all values provided' error goes away but causes a new "invalid type" error – Ben Parizek Nov 06 '16 at 07:25
1

@BenParizek: You shouldn’t do that, as you would no longer use the Schema.org vocabulary, but your own vocabulary instead. – unor Nov 06 '16 at 10:05
Changing @context to something else changes the meaning of the data. If you want to work with schema.org, you need to have that context (or fabricate one with the same definitions). Look up the JSON-LD spec if you want more details. – DieterDP Nov 06 '16 at 10:05
Understood. I wasn't proposing to do it as much as sharing a detail that seems to reveal which URL the error is trying to match when it fails validation in the testing tool right now. Worthwhile points to call out, however. – Ben Parizek Nov 06 '16 at 15:39

Bryan Heckler · Answer 3 · 2017-03-29T18:12:56.357

5

If you change your URL to "https://search.google.com/structured-data/testing-tool/", the tool will drop the error, just make sure before you put the code on your website that you update it.

Also, checking Search Console is likely a more reliable way (currently) to see if your markup has an error.

edited Mar 29 '17 at 18:12

answered Mar 29 '17 at 18:01

Bryan Heckler

105
4
10

score 0 · Answer 4 · answered Oct 27 '16 at 09:02

0

They can't prepopulate the examples in their documentation with the URL of the site you are going to write code for. They don't know what site you are writing code for.

answered Oct 27 '16 at 09:02

Quentin

914,110
126
1,211
1,335

Ok. But if I replace the snippet with my own data or other examples [Implementing JSON-LD](https://builtvisible.com/implementing-json-ld-wordpress/) I still get the same URL-error. – Piece of Code Oct 27 '16 at 09:10
Or does this only work on a live website? And how do I check that JSON-LD snippet? – Piece of Code Oct 27 '16 at 09:35
1

@PieceofCode — That testing tool, when you feed it copy/paste of the data instead of a URL, assumes the data is for `example.com`. You can either ignore errors about having the wrong hostname, change the data for the purposes of testing, or test in your live environment. – Quentin Oct 27 '16 at 09:49
Ok. Thanks for clearing that up. I was set on the wrong foot by validated screenshots in some blogposts but I assume those are from live/search console, not the testing-tool I referred to right? – Piece of Code Oct 27 '16 at 10:12
I voted your anwer up but because i'm new the vote is recorded and not displayed. – Piece of Code Oct 27 '16 at 10:13
@pieceofcode new users are restricted in voting answers up, it should show when your reputation is higher. Check SO's help section for more info. – Mousey Jan 01 '17 at 16:53
That's true but a) this is undocumented and b) only seems to be an issue for Organization entities; try it for a Website – Michael Feb 13 '17 at 09:50

score 0 · Answer 5 · answered Mar 02 '17 at 21:26

If you are pasting some code on the page and running it, Google assumes that it should be an example page. Instead do like this,

Test all other except "url"
Update the index.html on your server
Finally run test with your url (Choose New Test > Fetch URL)

Now you will not see the error again.

score 0 · Answer 6 · edited Mar 18 '17 at 03:45

0

I found that by implementing the JSON-LD snippet (with your correct details) in your website and clicking on 'New Test' at the top right of the Structured Data Test Page and using your correct URL it will not throw the error.

edited Mar 18 '17 at 03:45

Nathan Tuggy

2,237
27
30
38

answered Mar 18 '17 at 03:23

Jamie Lindsey

928
14
26

@Nathan I debated with myself whether to use the line you removed.. lol – Jamie Lindsey Mar 18 '17 at 04:08

score 0 · Answer 7 · answered May 03 '17 at 18:53

One reason this happens is because of the testing tool's UX. It seems kinda buggy to me.

First run a fresh test on a domain. You will see the Organization url is correct and there are no warnings since all matches.

Now, click in the source code (left pane) and add a single space somewhere harmless. You will see the domain disappears in the top bar:

You will also see the warning appear. Hitting "refresh" or starting a fresh test will correct the error again. I'm guessing the reason they do this is because when manually editing schema you are no longer, technically, reflecting the source from a domain.

Google SDTT error: "All values provided for http://www.example.com/ must have the same domain."

7 Answers7

Linked