KNOWLEDGE BASE
How do you implement internal linking and JSON-LD in e-commerce content?
Table of Contents — English
Which type should you choose for which content?
BlogPosting is a suitable candidate for a strategic blog post, and TechArticle for technical, instructional content. Schema.org defines the TechArticle type for technical and procedural articles. These choices describe the content type; on their own they do not qualify a page for a special result format in Google.
A post mentioning a product or payment concept does not make it a Product page. Product markup must be based on an actual product page and the related product data. Choose content types based on the page's main purpose, not on keywords.
How do you prepare internal links?
1. Identify the page's main question. An infrastructure selection article exists to support a decision; a data migration guide exists to teach the process.
2. Choose the relevant next question. From the phrase “migration plan” you can link to the data and URL migration guide. Not every page needs to link to every other page.
3. Write descriptive anchor text. Instead of “click here,” use text that describes the target, such as “stock reservation and order statuses.”
4. Place the link in the paragraph where the topic comes up, and support it with a related-content list at the end of the article. If the target is not yet published, the link should wait in the publishing plan.
5. If an address changes, check the links and redirects together. A link that cannot be crawled or that goes to the wrong target also misleads the user.
What information is JSON-LD built from?
For each article, create a title, description, language, persistent page URL and content ID. The publisher name must match the visible brand name. The author and publication date should be added only if the real information exists. The examples in this package do not use fake person names or publication dates that have not occurred.
The schema code can be placed in a script of type application/ld+json in the head or body of the published page. The JSON syntax must be valid, and quotation marks and special characters within the text must be escaped correctly. If a plugin already generates the same information, do not add a second, conflicting record.
Is FAQ markup mandatory?
No. A visible FAQ section that answers readers' questions is valuable on its own. Google has announced that the FAQ rich result feature will no longer be shown as of May 7, 2026. For this reason, you should not promise an expandable search result by adding FAQPage. The availability of the Schema.org vocabulary and a search engine's support for displaying it are separate matters.
The primary recommendation in this content package is BlogPosting or TechArticle. If separate FAQPage markup is preferred, it should cover only questions and answers that actually appear on the page. It should not be presented as a proven shortcut to being cited or to ranking higher.
How do you validate before publishing?
Open the page in a browser and check the title and text. Run the JSON through a syntax check, and the type and properties through the Schema Markup Validator. The Rich Results Test can be used for the relevant properties Google supports; these tools have different purposes.
Google's general structured data guidelines require that markup represent the visible content. Even if the code looks valid, false or hidden claims must not be added. The final check is that the text and the data say the same thing, in addition to technical validity.
What are the frequently asked questions?
What is the next step?
Share your content management system's current markup output with PROJX Digital, and we will check for conflicting records and content matching.
