#structureddata — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #structureddata, aggregated by home.social.
-
Declarative all the way down: Building PRONOM signatures with JSONID
by @beet_keeperPRONOM signatures are a form of declarative language, you describe the anticipated behavior in PRONOM’s regular expression syntax and tools like DROID, FIDO, and Siegfried will interpret those instructions and attempt to match them against different files to return a file format identification.
Normally, you will write PRONOM signatures by hand but doing so for file formats based on other file format building blocks can lead to inconsistencies. Bertrand Caron previously also recognized this in the XML formats that are described with PRONOM signatures on Wikidata.
XML can use single quotes
'(hex:0x27) and double quotes"(hex:0x22) for attribute data, and so, do we make a PRONOM signature with multiple sequences anticipating the use of either?The answer is more often than not likely to be yes, because the appearance of these values are often helpful for identifying boundaries for strings that we know must exist.
But the more file formats that we need to add to PRONOM that are based on foundational formats like XML, or JSON, or similar, the more inconsistencies will creep in, such as sequences that are looking specifically for one byte sequence over another.
The issue extends further if file formats allow data to appear at the beginning of file, or we need to account for a variable amount of white-space, or we want to start thinking about multi-byte character encoding.
We can, and in the XML issue described by myself and Caron, I think the recommendation is very much to create editorial standards for signatures for file formats based on other baseline, structured data formats like XML, JSON, YAML, and so on.
And standards are well and good, but what if tooling could help us?
For JSON this is exactly what I have tried to do in JSONID.
What does this feature look like? And what does it get us? Let’s take a look.
Continue reading “Declarative all the way down: Building PRONOM signatures with JSONID”…
#declarativeProgramming #digipres #DigitalPreservation #DROID #FIDO #FileFormatIdentification #FileFormats #JSON #jsonid #JSONL #NTTW #NTTW9 #PRONOM #RDM #ResearchData #siegfried #StructuredData #structuredText #TOML #YAML -
Declarative all the way down: Building PRONOM signatures with JSONID
by @beet_keeperPRONOM signatures are a form of declarative language, you describe the anticipated behavior in PRONOM’s regular expression syntax and tools like DROID, FIDO, and Siegfried will interpret those instructions and attempt to match them against different files to return a file format identification.
Normally, you will write PRONOM signatures by hand but doing so for file formats based on other file format building blocks can lead to inconsistencies. Bertrand Caron previously also recognized this in the XML formats that are described with PRONOM signatures on Wikidata.
XML can use single quotes ‘ (hex: 0x27) and double quotes ” (hex: 0x22) for attribute data, and so, do we make a PRONOM signature with multiple sequences anticipating the use of either?
The answer is more often than not likely to be yes, because the appearance of these values are often helpful for identifying boundaries for strings that we know must exist.
But the more file formats that we need to add to PRONOM that are based on foundational formats like XML, or JSON, or similar, the more inconsistencies will creep in, such as sequences that are looking specifically for one byte sequence over another.
The issue extends further if file formats allow data to appear at the beginning of file, or we need to account for a variable amount of white-space, or we want to start thinking about multi-byte character encoding.
We can, and in the XML issue described by myself and Caron, I think the recommendation is very much to create editorial standards for signatures for file formats based on other baseline, structured data formats like XML, JSON, YAML, and so on.
And standards are well and good, but what if tooling could help us?
For JSON this is exactly what I have tried to do in JSONID.
What does this feature look like? And what does it get us? Let’s take a look.
#declarativeProgramming #digipres #DigitalPreservation #DROID #FIDO #FileFormatIdentification #FileFormats #JSON #jsonid #JSONL #NTTW #NTTW9 #PRONOM #RDM #ResearchData #siegfried #StructuredData #structuredText #TOML #YAML -
Declarative all the way down: Building PRONOM signatures with JSONID
by @beet_keeperPRONOM signatures are a form of declarative language, you describe the anticipated behavior in PRONOM’s regular expression syntax and tools like DROID, FIDO, and Siegfried will interpret those instructions and attempt to match them against different files to return a file format identification.
Normally, you will write PRONOM signatures by hand but doing so for file formats based on other file format building blocks can lead to inconsistencies. Bertrand Caron previously also recognized this in the XML formats that are described with PRONOM signatures on Wikidata.
XML can use single quotes ‘ (hex: 0x27) and double quotes ” (hex: 0x22) for attribute data, and so, do we make a PRONOM signature with multiple sequences anticipating the use of either?
The answer is more often than not likely to be yes, because the appearance of these values are often helpful for identifying boundaries for strings that we know must exist.
But the more file formats that we need to add to PRONOM that are based on foundational formats like XML, or JSON, or similar, the more inconsistencies will creep in, such as sequences that are looking specifically for one byte sequence over another.
The issue extends further if file formats allow data to appear at the beginning of file, or we need to account for a variable amount of white-space, or we want to start thinking about multi-byte character encoding.
We can, and in the XML issue described by myself and Caron, I think the recommendation is very much to create editorial standards for signatures for file formats based on other baseline, structured data formats like XML, JSON, YAML, and so on.
And standards are well and good, but what if tooling could help us?
For JSON this is exactly what I have tried to do in JSONID.
What does this feature look like? And what does it get us? Let’s take a look.
#declarativeProgramming #digipres #DigitalPreservation #DROID #FIDO #FileFormatIdentification #FileFormats #JSON #jsonid #JSONL #NTTW #NTTW9 #PRONOM #RDM #ResearchData #siegfried #StructuredData #structuredText #TOML #YAML -
Declarative all the way down: Building PRONOM signatures with JSONID
by @beet_keeperPRONOM signatures are a form of declarative language, you describe the anticipated behavior in PRONOM’s regular expression syntax and tools like DROID, FIDO, and Siegfried will interpret those instructions and attempt to match them against different files to return a file format identification.
Normally, you will write PRONOM signatures by hand but doing so for file formats based on other file format building blocks can lead to inconsistencies. Bertrand Caron previously also recognized this in the XML formats that are described with PRONOM signatures on Wikidata.
XML can use single quotes ‘ (hex: 0x27) and double quotes ” (hex: 0x22) for attribute data, and so, do we make a PRONOM signature with multiple sequences anticipating the use of either?
The answer is more often than not likely to be yes, because the appearance of these values are often helpful for identifying boundaries for strings that we know must exist.
But the more file formats that we need to add to PRONOM that are based on foundational formats like XML, or JSON, or similar, the more inconsistencies will creep in, such as sequences that are looking specifically for one byte sequence over another.
The issue extends further if file formats allow data to appear at the beginning of file, or we need to account for a variable amount of white-space, or we want to start thinking about multi-byte character encoding.
We can, and in the XML issue described by myself and Caron, I think the recommendation is very much to create editorial standards for signatures for file formats based on other baseline, structured data formats like XML, JSON, YAML, and so on.
And standards are well and good, but what if tooling could help us?
For JSON this is exactly what I have tried to do in JSONID.
What does this feature look like? And what does it get us? Let’s take a look.
#declarativeProgramming #digipres #DigitalPreservation #DROID #FIDO #FileFormatIdentification #FileFormats #JSON #jsonid #JSONL #NTTW #NTTW9 #PRONOM #RDM #ResearchData #siegfried #StructuredData #structuredText #TOML #YAML -
Declarative all the way down: Building PRONOM signatures with JSONID
by @beet_keeperPRONOM signatures are a form of declarative language, you describe the anticipated behavior in PRONOM’s regular expression syntax and tools like DROID, FIDO, and Siegfried will interpret those instructions and attempt to match them against different files to return a file format identification.
Normally, you will write PRONOM signatures by hand but doing so for file formats based on other file format building blocks can lead to inconsistencies. Bertrand Caron previously also recognized this in the XML formats that are described with PRONOM signatures on Wikidata.
XML can use single quotes ‘ (hex: 0x27) and double quotes ” (hex: 0x22) for attribute data, and so, do we make a PRONOM signature with multiple sequences anticipating the use of either?
The answer is more often than not likely to be yes, because the appearance of these values are often helpful for identifying boundaries for strings that we know must exist.
But the more file formats that we need to add to PRONOM that are based on foundational formats like XML, or JSON, or similar, the more inconsistencies will creep in, such as sequences that are looking specifically for one byte sequence over another.
The issue extends further if file formats allow data to appear at the beginning of file, or we need to account for a variable amount of white-space, or we want to start thinking about multi-byte character encoding.
We can, and in the XML issue described by myself and Caron, I think the recommendation is very much to create editorial standards for signatures for file formats based on other baseline, structured data formats like XML, JSON, YAML, and so on.
And standards are well and good, but what if tooling could help us?
For JSON this is exactly what I have tried to do in JSONID.
What does this feature look like? And what does it get us? Let’s take a look.
#declarativeProgramming #digipres #DigitalPreservation #DROID #FIDO #FileFormatIdentification #FileFormats #JSON #jsonid #JSONL #NTTW #NTTW9 #PRONOM #RDM #ResearchData #siegfried #StructuredData #structuredText #TOML #YAML -
JSON-LD Explained for Personal Websites
https://hawksley.dev/blog/json-ld-explained-for-personal-websites/
#HackerNews #JSONLD #PersonalWebsites #WebDevelopment #StructuredData #TechExplained
-
JSON-LD Explained for Personal Websites
https://hawksley.dev/blog/json-ld-explained-for-personal-websites/
#HackerNews #JSONLD #PersonalWebsites #WebDevelopment #StructuredData #TechExplained
-
JSON-LD Explained for Personal Websites
https://hawksley.dev/blog/json-ld-explained-for-personal-websites/
#HackerNews #JSONLD #PersonalWebsites #WebDevelopment #StructuredData #TechExplained
-
JSON-LD Explained for Personal Websites
https://hawksley.dev/blog/json-ld-explained-for-personal-websites/
#HackerNews #JSONLD #PersonalWebsites #WebDevelopment #StructuredData #TechExplained
-
JSON-LD Explained for Personal Websites
https://hawksley.dev/blog/json-ld-explained-for-personal-websites/
#HackerNews #JSONLD #PersonalWebsites #WebDevelopment #StructuredData #TechExplained
-
“AI’s Biggest Challenge Is Not Technology”, Says Varun Thamba Of SAP
As enterprises move beyond experimentation and begin integrating artificial intelligence into core business operations, the conversation is shifting…
#Germany #DE #Europe #EU #Europa #SAP #agenticai #AIgovernance #EnterpriseAI #EnterpriseData #generativeAI #LargeLanguageModels(LLMs) #Reli #responsibleAI #RPT1.5 #sap #SAPAPAC #structureddata #TabularAI #VarunThamba
https://www.europesays.com/germany/39426/ -
Von SEO zu AEO, der Kassensturz: was eine maschinenlesbare Identität wirklich bringt
Ein gutes halbes Jahr nach meinem Beitrag von SEO zu AEO der ehrliche Kassensturz: was sich gehalten hat, was naiv war und was eine maschinenlesbare, verifizierbare Identität wirklich bringt. Dazu Zahlen zu Zero-Click und KI-Antworten, jeweils mit Quelle und Grenze, und warum llms.txt kein Wundermittel ist.https://www.kernel-error.de/2026/06/12/von-seo-zu-aeo-kassensturz-maschinenlesbare-identitaet/
-
Von SEO zu AEO, der Kassensturz: was eine maschinenlesbare Identität wirklich bringt
Ein gutes halbes Jahr nach meinem Beitrag von SEO zu AEO der ehrliche Kassensturz: was sich gehalten hat, was naiv war und was eine maschinenlesbare, verifizierbare Identität wirklich bringt. Dazu Zahlen zu Zero-Click und KI-Antworten, jeweils mit Quelle und Grenze, und warum llms.txt kein Wundermittel ist.https://www.kernel-error.de/2026/06/12/von-seo-zu-aeo-kassensturz-maschinenlesbare-identitaet/
-
Von SEO zu AEO, der Kassensturz: was eine maschinenlesbare Identität wirklich bringt
Ein gutes halbes Jahr nach meinem Beitrag von SEO zu AEO der ehrliche Kassensturz: was sich gehalten hat, was naiv war und was eine maschinenlesbare, verifizierbare Identität wirklich bringt. Dazu Zahlen zu Zero-Click und KI-Antworten, jeweils mit Quelle und Grenze, und warum llms.txt kein Wundermittel ist.https://www.kernel-error.de/2026/06/12/von-seo-zu-aeo-kassensturz-maschinenlesbare-identitaet/
-
Von SEO zu AEO, der Kassensturz: was eine maschinenlesbare Identität wirklich bringt
Ein gutes halbes Jahr nach meinem Beitrag von SEO zu AEO der ehrliche Kassensturz: was sich gehalten hat, was naiv war und was eine maschinenlesbare, verifizierbare Identität wirklich bringt. Dazu Zahlen zu Zero-Click und KI-Antworten, jeweils mit Quelle und Grenze, und warum llms.txt kein Wundermittel ist.https://www.kernel-error.de/2026/06/12/von-seo-zu-aeo-kassensturz-maschinenlesbare-identitaet/
-
Von SEO zu AEO, der Kassensturz: was eine maschinenlesbare Identität wirklich bringt
Ein gutes halbes Jahr nach meinem Beitrag von SEO zu AEO der ehrliche Kassensturz: was sich gehalten hat, was naiv war und was eine maschinenlesbare, verifizierbare Identität wirklich bringt. Dazu Zahlen zu Zero-Click und KI-Antworten, jeweils mit Quelle und Grenze, und warum llms.txt kein Wundermittel ist.https://www.kernel-error.de/2026/06/12/von-seo-zu-aeo-kassensturz-maschinenlesbare-identitaet/
-
Here it is: Eleventy Baseline v0.1.0-next.42 is on npm.
Mostly an SEO release. Not necessarily the answer to Life, the Universe and Everything.
<baseline-head> now emits a full structured-data graph plus Open Graph, Twitter and canonical, on its own, no per-site wiring. The graph is an adapter on Joost de Valk's seo-graph-core (of Yoast fame).
Release notes: https://www.eleventy-baseline.dev/release-notes/
#StructuredData #OpenSource #BuildInPublic
#11ty #eleventy-baseline #apleasantview -
Here it is: Eleventy Baseline v0.1.0-next.42 is on npm.
Mostly an SEO release. Not necessarily the answer to Life, the Universe and Everything.
<baseline-head> now emits a full structured-data graph plus Open Graph, Twitter and canonical, on its own, no per-site wiring. The graph is an adapter on Joost de Valk's seo-graph-core (of Yoast fame).
Release notes: https://www.eleventy-baseline.dev/release-notes/
#StructuredData #OpenSource #BuildInPublic
#11ty #eleventy-baseline #apleasantview -
Here it is: Eleventy Baseline v0.1.0-next.42 is on npm.
Mostly an SEO release. Not necessarily the answer to Life, the Universe and Everything.
<baseline-head> now emits a full structured-data graph plus Open Graph, Twitter and canonical, on its own, no per-site wiring. The graph is an adapter on Joost de Valk's seo-graph-core (of Yoast fame).
Release notes: https://www.eleventy-baseline.dev/release-notes/
#StructuredData #OpenSource #BuildInPublic
#11ty #eleventy-baseline #apleasantview -
Here it is: Eleventy Baseline v0.1.0-next.42 is on npm.
Mostly an SEO release. Not necessarily the answer to Life, the Universe and Everything.
<baseline-head> now emits a full structured-data graph plus Open Graph, Twitter and canonical, on its own, no per-site wiring. The graph is an adapter on Joost de Valk's seo-graph-core (of Yoast fame).
Release notes: https://www.eleventy-baseline.dev/release-notes/
#StructuredData #OpenSource #BuildInPublic
#11ty #eleventy-baseline #apleasantview -
FYI: Google and Schema.org finally show how the web uses structured data: Google and Schema.org release the first public dataset on structured data term adoption, covering millions of domains in CSV and JSON formats, updated monthly. https://ppc.land/google-and-schema-org-finally-show-how-the-web-uses-structured-data/ #Google #SchemaOrg #StructuredData #DataAnalysis #WebDevelopment
-
FYI: Google and Schema.org finally show how the web uses structured data: Google and Schema.org release the first public dataset on structured data term adoption, covering millions of domains in CSV and JSON formats, updated monthly. https://ppc.land/google-and-schema-org-finally-show-how-the-web-uses-structured-data/ #Google #SchemaOrg #StructuredData #DataAnalysis #WebDevelopment
-
FYI: Google and Schema.org finally show how the web uses structured data: Google and Schema.org release the first public dataset on structured data term adoption, covering millions of domains in CSV and JSON formats, updated monthly. https://ppc.land/google-and-schema-org-finally-show-how-the-web-uses-structured-data/ #Google #SchemaOrg #StructuredData #DataAnalysis #WebDevelopment
-
RT @carlos_darko: Google kündigt in Zusammenarbeit mit der Schema.org-Community ein neues Repository mit Nutzungsdaten verschiedener strukturierter Datenmarkierungen im Internet an.
mehr auf Arint.info
#DataAnalytics #Google #Schemaorg #SEO #StructuredData #WebDevelopment #arint_info
-
RT @carlos_darko: Google kündigt in Zusammenarbeit mit der Schema.org-Community ein neues Repository mit Nutzungsdaten verschiedener strukturierter Datenmarkierungen im Internet an.
mehr auf Arint.info
#DataAnalytics #Google #Schemaorg #SEO #StructuredData #WebDevelopment #arint_info
-
RT @carlos_darko: Google kündigt in Zusammenarbeit mit der Schema.org-Community ein neues Repository mit Nutzungsdaten verschiedener strukturierter Datenmarkierungen im Internet an.
mehr auf Arint.info
#DataAnalytics #Google #Schemaorg #SEO #StructuredData #WebDevelopment #arint_info
-
RT @carlos_darko: Google kündigt in Zusammenarbeit mit der Schema.org-Community ein neues Repository mit Nutzungsdaten verschiedener strukturierter Datenmarkierungen im Internet an.
mehr auf Arint.info
#DataAnalytics #Google #Schemaorg #SEO #StructuredData #WebDevelopment #arint_info
-
RT @carlos_darko: Google kündigt in Zusammenarbeit mit der Schema.org-Community ein neues Repository mit Nutzungsdaten verschiedener strukturierter Datenmarkierungen im Internet an.
mehr auf Arint.info
#DataAnalytics #Google #Schemaorg #SEO #StructuredData #WebDevelopment #arint_info
-
ICYMI: Google and Schema.org finally show how the web uses structured data: Google and Schema.org release the first public dataset on structured data term adoption, covering millions of domains in CSV and JSON formats, updated monthly. https://ppc.land/google-and-schema-org-finally-show-how-the-web-uses-structured-data/ #Google #SchemaOrg #StructuredData #DataAdoption #WebDevelopment
-
ICYMI: Google and Schema.org finally show how the web uses structured data: Google and Schema.org release the first public dataset on structured data term adoption, covering millions of domains in CSV and JSON formats, updated monthly. https://ppc.land/google-and-schema-org-finally-show-how-the-web-uses-structured-data/ #Google #SchemaOrg #StructuredData #DataAdoption #WebDevelopment
-
ICYMI: Google and Schema.org finally show how the web uses structured data: Google and Schema.org release the first public dataset on structured data term adoption, covering millions of domains in CSV and JSON formats, updated monthly. https://ppc.land/google-and-schema-org-finally-show-how-the-web-uses-structured-data/ #Google #SchemaOrg #StructuredData #DataAdoption #WebDevelopment
-
RT @carlos_darko: Google kündigt in Zusammenarbeit mit der Schema.org-Community ein neues Repository mit Nutzungsdaten der verschiedenen strukturierten Datenmarkierungen im Internet an. Diese Daten, die monatlich aktualisiert werden, sind für Analyse oder Download (im CSV- oder JSON-Format) über das offizielle GitHub von Schema verfügbar: https://github.com/schemaorg/schemaorg/tree/main/data/publicstats/google. Sie bieten eine Möglichkeit, die Adoption strukturierten Daten über die Zeit hinweg zu verfolgen und bei Unsicherheit zwischen ähnlichen Optionen diejenige mit höherer Implementierungsrate zu wählen. Das offizielle Statement von Schema finden Sie unter: https://blog.schema.org/2026/06/04/announcing-the-schema-org-usage-statistics-dataset/ sowie weitere Informationen unter: https://schema.org/docs/usagestats.html
mehr auf Arint.info
#DataAnalytics #GoogleAnnouncements #Schemaorg #SEO #StructuredData #WebDevelopment #arint_info
-
RT @carlos_darko: Google kündigt in Zusammenarbeit mit der Schema.org-Community ein neues Repository mit Nutzungsdaten der verschiedenen strukturierten Datenmarkierungen im Internet an. Diese Daten, die monatlich aktualisiert werden, sind für Analyse oder Download (im CSV- oder JSON-Format) über das offizielle GitHub von Schema verfügbar: https://github.com/schemaorg/schemaorg/tree/main/data/publicstats/google. Sie bieten eine Möglichkeit, die Adoption strukturierten Daten über die Zeit hinweg zu verfolgen und bei Unsicherheit zwischen ähnlichen Optionen diejenige mit höherer Implementierungsrate zu wählen. Das offizielle Statement von Schema finden Sie unter: https://blog.schema.org/2026/06/04/announcing-the-schema-org-usage-statistics-dataset/ sowie weitere Informationen unter: https://schema.org/docs/usagestats.html
mehr auf Arint.info
#DataAnalytics #GoogleAnnouncements #Schemaorg #SEO #StructuredData #WebDevelopment #arint_info
-
RT @carlos_darko: Google kündigt in Zusammenarbeit mit der Schema.org-Community ein neues Repository mit Nutzungsdaten der verschiedenen strukturierten Datenmarkierungen im Internet an. Diese Daten, die monatlich aktualisiert werden, sind für Analyse oder Download (im .csv- oder .json-Format) über das offizielle GitHub von Schema verfügbar: https://github.com/schemaorg/schemaorg/tree/main/data/publicstats/google. Sie bieten eine Möglichkeit, die Adoption strukturierte Daten im Laufe der Zeit zu verfolgen und bei Unsicherheit zwischen ähnlichen Optionen diejenige mit höherer Implementierungsrate zu wählen. Das offizielle Schema-Kommuniqué finden Sie unter: https://blog.schema.org/2026/06/04/announcing-the-schema-org-usage-statistics-dataset/ sowie weitere Informationen unter: https://schema.org/docs/usagestats.html
mehr auf Arint.info
#DataAnalytics #GoogleAnnouncement #Schemaorg #SEO #StructuredData #WebSemantics #arint_info
-
RT @carlos_darko: Google kündigt in Zusammenarbeit mit der Schema.org-Community ein neues Repository mit Nutzungsdaten der verschiedenen strukturierten Datenmarkierungen im Internet an. Diese Daten, die monatlich aktualisiert werden, sind für Analyse oder Download (im .csv- oder .json-Format) über das offizielle GitHub von Schema verfügbar: https://github.com/schemaorg/schemaorg/tree/main/data/publicstats/google. Sie bieten eine Möglichkeit, die Adoption strukturierte Daten im Laufe der Zeit zu verfolgen und bei Unsicherheit zwischen ähnlichen Optionen diejenige mit höherer Implementierungsrate zu wählen. Das offizielle Schema-Kommuniqué finden Sie unter: https://blog.schema.org/2026/06/04/announcing-the-schema-org-usage-statistics-dataset/ sowie weitere Informationen unter: https://schema.org/docs/usagestats.html
mehr auf Arint.info
#DataAnalytics #GoogleAnnouncement #Schemaorg #SEO #StructuredData #WebSemantics #arint_info
-
Google and Schema.org finally show how the web uses structured data: Google and Schema.org release the first public dataset on structured data term adoption, covering millions of domains in CSV and JSON formats, updated monthly. https://ppc.land/google-and-schema-org-finally-show-how-the-web-uses-structured-data/ #StructuredData #SchemaOrg #Google #SEO #WebDevelopment
-
Google and Schema.org finally show how the web uses structured data: Google and Schema.org release the first public dataset on structured data term adoption, covering millions of domains in CSV and JSON formats, updated monthly. https://ppc.land/google-and-schema-org-finally-show-how-the-web-uses-structured-data/ #StructuredData #SchemaOrg #Google #SEO #WebDevelopment
-
Google and Schema.org finally show how the web uses structured data: Google and Schema.org release the first public dataset on structured data term adoption, covering millions of domains in CSV and JSON formats, updated monthly. https://ppc.land/google-and-schema-org-finally-show-how-the-web-uses-structured-data/ #StructuredData #SchemaOrg #Google #SEO #WebDevelopment
-
Google and Schema.org finally show how the web uses structured data: Google and Schema.org release the first public dataset on structured data term adoption, covering millions of domains in CSV and JSON formats, updated monthly. https://ppc.land/google-and-schema-org-finally-show-how-the-web-uses-structured-data/ #StructuredData #SchemaOrg #Google #SEO #WebDevelopment
-
What Is Content Engineering, and How Do You Do It?, by @lou-lin.bsky.social (@ahrefs):
https://ahrefs.com/blog/what-is-content-engineering/?ref=frontenddogma.com
-
What Is Content Engineering, and How Do You Do It?, by @lou-lin.bsky.social (@ahrefs):
https://ahrefs.com/blog/what-is-content-engineering/?ref=frontenddogma.com
-
What Is Content Engineering, and How Do You Do It?, by @lou-lin.bsky.social (@ahrefs):
https://ahrefs.com/blog/what-is-content-engineering/?ref=frontenddogma.com
-
What Is Content Engineering, and How Do You Do It?, by @lou-lin.bsky.social (@ahrefs):
https://ahrefs.com/blog/what-is-content-engineering/?ref=frontenddogma.com
-
What Is Content Engineering, and How Do You Do It?, by @lou-lin.bsky.social (@ahrefs):
https://ahrefs.com/blog/what-is-content-engineering/?ref=frontenddogma.com
-
SAP AI Data Push With Dremio And Prior Labs Raises Valuation Question
Make better investment decisions with Simply Wall St’s easy, visual tools that give you a competitive edge. SAP…
#Germany #DE #Europe #EU #Europa #SAP #businessapplications #DataInfrastructure #datalakehouse #Dremio #priorlabs #sap #structureddata
https://www.europesays.com/germany/25859/ -
1,885 pages had schema markup added and their AI citation rates tracked. The result? Almost no movement.
Cited pages are more likely to have JSON-LD - but that reflects technical discipline, not a lever you can pull. Authority, content clarity, and domain trust are doing the work.
#GEO #AISearch #StructuredData
https://www.digiconomy.online/insights/schema-markup-ai-citations-correlation/
-
When geopolitics hits the wallet, it hits the advisor’s office too.
Stock and finance charts over a holographic illustration of oil pump infrastructure. – CoreDESIG…
#UnitedStates #US #USA #america #clientbehavior #conversations #everydayAmericans #financialadvisor #financialpressure #financialpressures #geopolitics #macroeconomicshocks #oilprices #Politics #stressandanxiety #structureddata #unitedstatesofamerica #UnitedStatesPolitics #USPolitics #usapolitics
https://www.europesays.com/2949430/ -
Schema Markup ist die einzige Sprache, die Suchmaschinen ohne Interpretation verstehen. 🗣️Kein Raten, kein NLP, kein Kontext-Ableiten – du sagst Google direkt: Das ist ein Produkt, das kostet 29 €, es hat 4,7 Sterne. Wer kein strukturiertes Markup nutzt, überlässt die Kommunikation dem Zufall. Und Zufall ist keine SEO-Strategie.
-
Schema Markup ist die einzige Sprache, die Suchmaschinen ohne Interpretation verstehen. 🗣️Kein Raten, kein NLP, kein Kontext-Ableiten – du sagst Google direkt: Das ist ein Produkt, das kostet 29 €, es hat 4,7 Sterne. Wer kein strukturiertes Markup nutzt, überlässt die Kommunikation dem Zufall. Und Zufall ist keine SEO-Strategie.
-
Schema Markup ist die einzige Sprache, die Suchmaschinen ohne Interpretation verstehen. 🗣️Kein Raten, kein NLP, kein Kontext-Ableiten – du sagst Google direkt: Das ist ein Produkt, das kostet 29 €, es hat 4,7 Sterne. Wer kein strukturiertes Markup nutzt, überlässt die Kommunikation dem Zufall. Und Zufall ist keine SEO-Strategie.
-
Schema Markup ist die einzige Sprache, die Suchmaschinen ohne Interpretation verstehen. 🗣️Kein Raten, kein NLP, kein Kontext-Ableiten – du sagst Google direkt: Das ist ein Produkt, das kostet 29 €, es hat 4,7 Sterne. Wer kein strukturiertes Markup nutzt, überlässt die Kommunikation dem Zufall. Und Zufall ist keine SEO-Strategie.
-
Schema Markup ist die einzige Sprache, die Suchmaschinen ohne Interpretation verstehen. 🗣️Kein Raten, kein NLP, kein Kontext-Ableiten – du sagst Google direkt: Das ist ein Produkt, das kostet 29 €, es hat 4,7 Sterne. Wer kein strukturiertes Markup nutzt, überlässt die Kommunikation dem Zufall. Und Zufall ist keine SEO-Strategie.
-
Extra zesty post by Drew Tendero
Local search engine optimization: how to get found by nearby customers
Learn what local SEO is, why it matters, and how to optimize your business for local search. From Google Business Profile to reviews, schema markup, and local content strategies.
#SEO #SEOStrategies #SearchEngineOptimization #ContentStrategy #Google #StructuredData #SchemaMarkup
https://freshjuice.dev/blog/local-search-engine-optimization/
-
Neu im Forum:
Strukturierte Daten für Portfolio/Referenzen
https://t3forum.net/d/1100-strukturierte-daten-fuer-portfolioreferenzen
-
Neu im Forum:
Strukturierte Daten für Portfolio/Referenzen
https://t3forum.net/d/1100-strukturierte-daten-fuer-portfolioreferenzen
-
Neu im Forum:
Strukturierte Daten für Portfolio/Referenzen
https://t3forum.net/d/1100-strukturierte-daten-fuer-portfolioreferenzen
-
Neu im Forum:
Strukturierte Daten für Portfolio/Referenzen
https://t3forum.net/d/1100-strukturierte-daten-fuer-portfolioreferenzen
-
Neu im Forum:
Strukturierte Daten für Portfolio/Referenzen
https://t3forum.net/d/1100-strukturierte-daten-fuer-portfolioreferenzen
-
Adding AI Usage Metadata to JSON-LD Structured Data
https://rmendes.net/articles/2026/03/03/adding-ai-usage-metadata-to
-
Adding AI Usage Metadata to JSON-LD Structured Data
https://rmendes.net/articles/2026/03/03/adding-ai-usage-metadata-to