I Inspected ratecity.com.au Schema and Here's What I Found
HTML-код
- Опубликовано: 13 авг 2024
- RateCity is a well-known 🇦🇺 brand in the YMYL space. Sally is often on the news commenting on the RBA's monetary policy re: interest rates.
As someone who has gone through the process of getting a home loan and is looking to refinance, I was intrigued when I saw its home loan comparison page rank, so I took a look 👀 (as any SEO would).
You would think that a site such as ratecity.com.au would have advanced nested schema 🙈
Issues found:
❌ Homepage has no schema
❌ Author pages have no schema
❌ No URIs
❌ Unoptimised nested schema markup
In this video, I do a live audit of their /home-loans URL and write JSON-LD from scratch based on the content on the page.
You'll see me:
👉 Reference Organization schema URI
👉 Reference Person schema using the Author property
👉 Connect DataSet schema to WebPage schema
👉 Connect FAQPage schema to WebPage schema
👉 Use Merkle's tool to generate FAQPage schema
👉 Test JSON-LD at various stages using schema.org validator
Jump to:
00:00 Who/what is Rate City?
01:44 How to see existing schema markup for any URL
02:45 What is unstructured data?
04:39 Live audit of schema markup
10:24 Watch me write JSON-LD from scratch
18:16 Describing content author(s) using Person schema
21:03 How to use reviewedBy item property
25:07 Visualising the knowledge graph created with schema markup
26:58 Building FAQPage schema via generator
33:40 Nesting FAQPage as part of WebPage schema
35:51 Recap of the schema markup
📌 Learn the basics of semantic SEO in this written guide 👇🏽
www.danielkcheung.com.au/how-...
_________
My tool/tech stack for Scheming Schemas:
・FAQPage generator 👉 technicalseo.com/tools/schema...
・Schema.org validator 👉 validator.schema.org
・Visual Studio Code 👉 code.visualstudio.com
・JSON-LD playground 👉 json-ld.org/playground/
_________
👋 I'm Daniel Cheung.
Outside of my in-house enterprise SEO day job, I am a full-stack SEO consultant, advisor, and educator.
Follow Schema Schemas for:
✅ Actionable semantic SEO tips
📣 Step-by-step JSON-LD construction
Or, if you have a complex problem that needs an immediate solution, reach out via my website contact form.
🎯 www.danielkcheung.com/services/
📩 www.danielkcheung.com/contact/
I've learnt a few things again. Thank you for this video on writing schema code.
Wow, high quality stuff here.
Nice one mate!
Thanks!
Great stuff Daniel, keen to see the rise of the schema king
A schema king already exists! And it’s not me 😗
Soooo good, thanks!
Glad you like it!
looking forward to this :)
Hope you like it!
Hi Daniel, very interesting video!
Just a question regarding links into FAQ structured data.
Based on some experience, I've seen Google tends to remove FAQ snippet from the SERPs if we "push" too hard on FAQ schema putting links or emojis into it.
I mean, even if Google can properly render it like you showed using the rich snippet tester.
Have you had some experience like that or it's just that I'm, after all, a spammer =D?
Thank you!
It appears Google has decided to not show FAQ rich results on mobile and desktop SERPs since early May. Looks like the good run is over! 🫠
FYI, for the last few weeks, I couldn’t even get the RRT to preview my FAQ schema! Could be an IP thing or a sign of what’s happening 🤷🏻♂️
Hi Daniel, could you have content on structured Data basics
It’s coming!
Hi Daniel. This is great. I am subscribed for more! Just wonder though, thinking of Google - do you have any insight as to whether they use cross-page node identifiers (@id) to build properties? I ask because you seem to be adding the Organization @id (assuming it exists on the homepage) as if it would work cross-page. To the best of my knowledge, Google doesn't connect schema objects like this (yet at least).
Great question and to be honest, I don't know whether or not Google will follow to the location of the URI - I certainly *hope* they do. This is definitely a question worthy of posing to John during Office Hours, or perhaps to Dave or Martha.
@@SchemingSchemas @IanBooth Hello guys, do you have any update regarding this point by chance?
Google does not follow cross-page nodes.
@@SchemingSchemas So, @id's use goes no further than the page it's created on? Does this mean that connecting to the organization schema through its @id on all the pages other than the homepage is basically pointless? That would mean having to recreate the same organization schema on every single page (as the publisher). Same would apply for the Person schema as the author.
This is where the concept and practice of entity homes as defined by Jason Barnard (Kalicube) comes into play. That is, instead of duplicating schema markup on each page, the identifier property can be used to tell crawlers the location of the entity home.
This way you’re only referencing schema markup that has front-end content represented and you’re not adding bloat to the page code.
Therefore, you should not describe in full detail a Person or Organizatiin entity on each page, but rather, you describe the entity in full on its corresponding entity home (this can be a profile page or about page) then reference the identifier using no more than 3-5 properties.