In Future Release How To Edit Organization Schema

[bassangler]

I noticed the Organization schema works IF the TLD is the forums. However, that's not the case for us.  Instead, IC a directory off the the TLD (i.e. https://TLD/forums).  In this instance, the schema ends up like this:

@type	Organization
@id	https://www.TLD/forums/#organization
mainEntityOfPage	https://www.TLD/forums/
name	Name of Forums
url	https://www.TLD/forums/

 

Where it should be:

@type	Organization
@id	https://www.TLD/#organization
mainEntityOfPage	https://www.TLD/
name	Name of Website
url	https://www.TLD/

 

Is there a method to fix this?

 

[Jim M]

This would be correct as your community is installed in your "forums" directory. Thus, the software uses that URL. To change this, it would not be advised and require a customization.

[bassangler]

Well, no, it's not correct.  The schema is wrong.  

You're saying it cannot be fixed?  Seems like a bug then, because you should be able to edit it for instances like this.

[Marc Stridgen]

I'm a little confused as to what you believe to be incorrect there. Its generating what you have your software installed under. Your root URL is not our software

[bassangler]

I get the software assumes it's installed at the root directory, hence the way the Schema is coded.

 

But it's not installed in the root directory, so the Schema information is incorrect. The software has no provision for that use case (installed in something OTHER than the root).  That is the problem.

[Matt]

I understand what you mean.

You're saying your site is my-site.com, and you have created a directory 'forums' and put the forums in there, so the JSON should report the site as 'my-site.com' but it's reporting 'my-site.com/forums'. I'll open an issue.

[bassangler]

Yes, plus mainEntityOfPage, Name, and URL values (see my OP for example).

Thank you!

Edited April 18 by bassangler

[Matt]

This should make it into the June release.