{"id":22789,"date":"2026-08-29T06:40:02","date_gmt":"2026-08-29T04:40:02","guid":{"rendered":"https:\/\/www.curiaweb.ch\/?post_type=docs&p=22789"},"modified":"2026-08-29T06:40:03","modified_gmt":"2026-08-29T04:40:03","password":"","slug":"subdomain-or-subdirectory-seo","status":"publish","type":"docs","link":"https:\/\/www.curiaweb.ch\/en\/hilfe\/domains-dns\/subdomain-oder-unterverzeichnis-seo\/","title":{"rendered":"Subdomain or subdirectory: Which is better for SEO?"},"content":{"rendered":"

When you want to build a new section of your website, the question often arises: should the content be located under a subdomain or in a subdirectory?<\/p>\n\n\n\n

Both variants are technically possible and can be indexed by search engines. The decision should therefore not be based on the blanket assumption that a subdomain or a subdirectory inherently ranks better on Google.<\/p>\n\n\n\n

More important are the technical architecture of your website, the topical relevance, internal linking, user navigation, and the question of whether a section should be operated intentionally independently.<\/p>\n\n\n\n

\n

Briefly explained:<\/strong> A subdirectory like example.ch\/blog\/<\/code> is an area within the same website or the same hostname. A subdomain like blog.example.ch<\/code> is a separate hostname instead. For SEO, there is no simple rule of \u201esubdirectory good, subdomain bad\u201c.<\/p>\n<\/blockquote>\n\n\n\n

What is a subdirectory?<\/h2>\n\n\n\n

A subdirectory is located within the URL structure of an existing website.<\/p>\n\n\n\n

Examples:<\/p>\n\n\n\n

https:\/\/example.ch\/blog\/\nhttps:\/\/example.ch\/hilfe\/\nhttps:\/\/example.ch\/shop\/<\/code><\/pre>\n\n\n\n
The main domain or hostname remains the same:<\/p>\n\n\n\n
example.ch<\/code><\/p>\n\n\n\n
Only the path behind the domain name changes.<\/p>\n\n\n\n
At CURIAWEB, for example, the knowledge base is also structured according to this principle:<\/p>\n\n\n\n
\nhttps:\/\/www.curiaweb.ch\/hilfe\n<\/div><\/figure>\n\n\n\n
The knowledge base is therefore part of the existing website and not a separate hostname.<\/p>\n\n\n\n
What is a subdomain?<\/h2>\n\n\n\n
A subdomain precedes the actual domain name.<\/p>\n\n\n\n
Examples:<\/p>\n\n\n\n
blog.example.ch\nshop.example.ch\nsupport.example.ch\nmy.example.ch<\/code><\/pre>\n\n\n\n
Technically, a subdomain is a separate hostname and can point to a different infrastructure independently of the main website.<\/p>\n\n\n\n
For example, can<\/p>\n\n\n\n
example.ch\nshop.example.ch<\/code><\/pre>\n\n\n\n
be operated on different servers.<\/p>\n\n\n\n
What is the technical difference?<\/h2>\n\n\n\n
For a subdirectory, the hostname remains the same:<\/p>\n\n\n\n
example.ch\/blog\/\nexample.ch\/shop\/\nexample.ch\/hilfe\/<\/code><\/pre>\n\n\n\n
By contrast, a subdomain creates an additional hostname:<\/p>\n\n\n\n
blog.example.ch\nshop.example.ch\nhilfe.example.ch<\/code><\/pre>\n\n\n\n
This difference has technical consequences. For example, a subdomain may require its own DNS records, its own hosting configuration, and its own SSL\/TLS certificate or corresponding certificate coverage.<\/p>\n\n\n\n
We explain what role DNS records play in this at DNS Records Explained: A, AAAA, CNAME, MX, TXT, and CAA<\/a>.<\/p>\n\n\n\n
Is a subdomain a separate domain?<\/h2>\n\n\n\n
No.<\/p>\n\n\n\n
At<\/p>\n\n\n\n
blog.example.ch<\/code><\/p>\n\n\n\n
is example.ch<\/code> still the registered domain. blog<\/code> is a subdomain or hostname set up underneath it.<\/p>\n\n\n\n
You therefore normally do not have to register a new domain for every subdomain.<\/p>\n\n\n\n
We explain the differences between domain and URL at Website, Domain, and URL: What is the difference?<\/a>.<\/p>\n\n\n\n
Is a subdirectory better for SEO?<\/h2>\n\n\n\n
Not fundamentally.<\/p>\n\n\n\n
However, subdirectories have an important structural advantage: content that is clearly part of the same website can be organized very easily within a shared URL structure.<\/p>\n\n\n\n
For example, a corporate blog could be found at<\/p>\n\n\n\n
example.ch\/blog\/<\/code><\/p>\n\n\n\n
lie and the knowledge base under<\/p>\n\n\n\n
example.ch\/help\/<\/code>.<\/p>\n\n\n\n
This makes it immediately recognizable to users that this content belongs to the main website.<\/p>\n\n\n\n
However, this alone does not guarantee better rankings. Content quality, search intent, internal linking, crawlability, technical quality, and many other factors remain decisive.<\/p>\n\n\n\n
\n
Important:<\/strong> A subdirectory does not automatically get good rankings just because the main domain is already established. Content in a subdirectory must also be relevant, crawlable, and of convincing quality.<\/p>\n<\/blockquote>\n\n\n\n
Is a subdomain bad for SEO?<\/h2>\n\n\n\n
No.<\/p>\n\n\n\n
Subdomains can be crawled and indexed by search engines and can also achieve good rankings.<\/p>\n\n\n\n
Therefore, a subdomain is not automatically an SEO mistake.<\/p>\n\n\n\n
Rather, what is crucial is whether the chosen structure makes sense for the respective website area and is implemented cleanly from a technical standpoint.<\/p>\n\n\n\n
Does Google treat a subdomain as a separate website?<\/h2>\n\n\n\n
A blanket statement like \u201eGoogle treats every subdomain completely like a foreign website\u201c is too simplistic.<\/p>\n\n\n\n
Technically, a subdomain is a separate hostname. Google also differentiates between domains, subdomains, and directories in various functions and systems.<\/p>\n\n\n\n
However, that does not automatically mean it results in a blanket SEO disadvantage.<\/p>\n\n\n\n
\n
Note:<\/strong> \u201eCustom hostname\u201c and \u201eworse rankings\u201c are two completely different statements. No automatic ranking disadvantage can be derived from the technical independence of a subdomain.<\/p>\n<\/blockquote>\n\n\n\n
When is a subdirectory useful?<\/h2>\n\n\n\n
A subdirectory is often a good choice when the new section clearly belongs to the existing website.<\/p>\n\n\n\n
Typical examples are:<\/p>\n\n\n\n
example.ch\/blog\/\nexample.ch\/guide\/\nexample.ch\/help\/\nexample.ch\/references\/\nexample.ch\/products\/<\/code><\/pre>\n\n\n\n
The content can be integrated into a common navigation, internal linking, and information architecture.<\/p>\n\n\n\n
Therefore, a subdirectory is often a very natural solution for a corporate blog or a knowledge base.<\/p>\n\n\n\n
When does a subdomain make sense?<\/h2>\n\n\n\n
A subdomain can be useful if a section is to be technically or functionally clearly separated from the main website.<\/p>\n\n\n\n
Examples can be:<\/p>\n\n\n\n
my.example.ch\napp.example.ch\nstatus.example.ch\ndev.example.ch<\/code><\/pre>\n\n\n\n
For example, a customer portal, a web application, or a status system may use completely different software and infrastructure than the public corporate website.<\/p>\n\n\n\n
In such cases, technical separation can be more important than the desire to operate all content under a common directory path.<\/p>\n\n\n\n
Can a subdomain be hosted on a different server?<\/h2>\n\n\n\n
Yes.<\/p>\n\n\n\n
This is one of the major technical advantages of subdomains.<\/p>\n\n\n\n
For example, the main domain can point to a web server:<\/p>\n\n\n\n
example.ch<\/code><\/p>\n\n\n\n
while<\/p>\n\n\n\n
app.example.ch<\/code><\/p>\n\n\n\n
points to a different infrastructure via its own DNS record.<\/p>\n\n\n\n
This enables a clean separation of different applications and systems.<\/p>\n\n\n\n
Can a subdirectory be on another server?<\/h2>\n\n\n\n
Technically this is also possible, but usually more complex.<\/p>\n\n\n\n
Since<\/p>\n\n\n\n
example.ch\/app\/<\/code><\/p>\n\n\n\n
the same hostname is used as for the main website, the separation is not simply done via a separate DNS entry for the directory.<\/p>\n\n\n\n
Instead, corresponding reverse proxy, web server or application rules would be required, for example.<\/p>\n\n\n\n
DNS works with hostnames and not with URL paths like \/app\/<\/code>.<\/p>\n\n\n\n
\n
Briefly explained:<\/strong> DNS can app.example.ch<\/code> tax separately, but not directly example.ch\/app\/<\/code>. The path only becomes relevant after connecting to the web server.<\/p>\n<\/blockquote>\n\n\n\n
What is better for a blog?<\/h2>\n\n\n\n
If the blog is a normal part of the company website, a subdirectory is often the simpler and more logical structure:<\/p>\n\n\n\n
example.ch\/blog\/<\/code><\/p>\n\n\n\n
This allows the blog to be integrated directly into the navigation, internal linking, and the rest of the website structure.<\/p>\n\n\n\n
A subdomain like<\/p>\n\n\n\n
blog.example.ch<\/code><\/p>\n\n\n\n
can still make sense if there are technical or organizational reasons for a separation.<\/p>\n\n\n\n
Solely for SEO reasons, an existing, functioning blog structure should not be reorganized without a concrete necessity.<\/p>\n\n\n\n
What is better for a knowledge base?<\/h2>\n\n\n\n
Here too, the decision depends on the technical and organizational structure.<\/p>\n\n\n\n
If the knowledge base is part of the main website, it is a good idea, for example:<\/p>\n\n\n\n
example.ch\/help\/<\/code><\/p>\n\n\n\n
If, on the other hand, a completely standalone support system or an external application is used, a structure like<\/p>\n\n\n\n
support.example.ch<\/code><\/p>\n\n\n\n
be more technically sound.<\/p>\n\n\n\n
The crucial factor is not the claim that one variant is fundamentally stronger for SEO, but rather which architecture for content and system makes sense in the long term.<\/p>\n\n\n\n
What is better for an online shop?<\/h2>\n\n\n\n
If the shop and main website are closely linked and use the same content management system, a subdirectory can make sense:<\/p>\n\n\n\n
example.ch\/shop\/<\/code><\/p>\n\n\n\n
On the other hand, a technically completely separate shop system could under<\/p>\n\n\n\n
shop.example.ch<\/code><\/p>\n\n\n\n
be operated.<\/p>\n\n\n\n
Here too, the decision should be made based on technical requirements, maintainability, user guidance, and the long-term URL structure.<\/p>\n\n\n\n
What is better for a customer area?<\/h2>\n\n\n\n
For a customer area, a subdomain is often a very sensible solution.<\/p>\n\n\n\n
For example:<\/p>\n\n\n\n
my.example.ch<\/code><\/p>\n\n\n\n
This allows the customer area to be operated technically independently of the public website.<\/p>\n\n\n\n
This is especially practical when different applications are used.<\/p>\n\n\n\n
Furthermore, a customer portal does not necessarily have to meet the same SEO requirements as publicly indexable informational or product pages.<\/p>\n\n\n\n
What about internal links?<\/h2>\n\n\n\n
Regardless of the chosen structure, the internal linking should be set up sensibly.<\/p>\n\n\n\n
A blog, guide, or help section should not exist in isolation if its content is relevant to visitors of the main website.<\/p>\n\n\n\n
Link thematically related content wherever the link actually helps the user.<\/p>\n\n\n\n
Clear navigation and information architecture are more important than trying to generate rankings through a specific URL structure alone.<\/p>\n\n\n\n
What happens to backlinks?<\/h2>\n\n\n\n
Backlinks point to specific URLs.<\/p>\n\n\n\n
An external link to<\/p>\n\n\n\n
\nhttps:\/\/example.ch\/blog\/artikel\n<\/div><\/figure>\n\n\n\n
is therefore not the same link as one on<\/p>\n\n\n\n
\nhttps:\/\/blog.example.ch\/artikel\/.\n<\/div><\/figure>\n\n\n\n
When existing content is moved from one structure to another, the URLs change, and the old addresses should be redirected to the new destinations accordingly.<\/p>\n\n\n\n
Should I switch from a subdomain to a subdirectory for SEO reasons?<\/h2>\n\n\n\n
Not solely based on the blanket statement that subdirectories are always better.<\/p>\n\n\n\n
A change of<\/p>\n\n\n\n
blog.example.ch<\/code><\/p>\n\n\n\n
to<\/p>\n\n\n\n
example.ch\/blog\/<\/code><\/p>\n\n\n\n
changes the URLs of the entire section.<\/p>\n\n\n\n
This results in a website migration. Existing URLs must be redirected to their new destinations, and internal links, canonical tags, sitemaps, and other technical signals must be updated accordingly.<\/p>\n\n\n\n
Therefore, a functioning and established structure should not be migrated without a specific technical, organizational, or strategic reason.<\/p>\n\n\n\n
\n
Attention:<\/strong> A URL migration solely due to a perceived \u201esubdomain SEO disadvantage\u201c can create more effort and risk than it brings benefits.<\/p>\n<\/blockquote>\n\n\n\n
What do I need to consider during a migration?<\/h2>\n\n\n\n
When content is moved from a subdomain to a subdirectory or in the reverse direction, a suitable new destination should be defined for each relevant old URL.<\/p>\n\n\n\n
For example:<\/p>\n\n\n\n
blog.example.ch\/artikel-a\/\n        \u2193\nexample.ch\/blog\/artikel-a\/\n\nblog.example.ch\/artikel-b\/\n        \u2193\nexample.ch\/blog\/artikel-b\/<\/code><\/pre>\n\n\n\n
For permanently moved content, appropriate permanent server-side redirects should be used.<\/p>\n\n\n\n
Internal links, XML sitemaps, and canonical tags must also match the new structure.<\/p>\n\n\n\n
What about duplicate content?<\/h2>\n\n\n\n
It can become problematic if identical or nearly identical content remains accessible under multiple URLs at the same time.<\/p>\n\n\n\n
For example:<\/p>\n\n\n\n
blog.example.ch\/ratgeber\/\nexample.ch\/blog\/ratgeber\/<\/code><\/pre>\n\n\n\n
If both versions permanently serve the same content, it must be clear to search engines which URL is the preferred or canonical version.<\/p>\n\n\n\n
In a real migration, it is usually cleaner to permanently redirect the old URL to the new URL instead of running both structures in parallel indefinitely with identical content.<\/p>\n\n\n\n
Can I publish the same content on a subdomain and a subdirectory?<\/h2>\n\n\n\n
Technically that is possible, but usually not sensible for the same purpose.<\/p>\n\n\n\n
Several identical URLs do not automatically improve content. Instead, they can create unnecessary duplicates and complicate website analysis.<\/p>\n\n\n\n
If there is no objective reason for multiple versions, content should have a clear primary URL.<\/p>\n\n\n\n
How does Google handle canonical URLs?<\/h2>\n\n\n\n
When Google finds multiple identical or very similar pages, it evaluates them together for canonicalization.<\/p>\n\n\n\n
Website operators can, for example, with redirects, rel=\"canonical\"<\/code> and provide hints regarding the preferred URL through consistent sitemap data.<\/p>\n\n\n\n
However, Google may ultimately choose a different URL as canonical if the existing signals suggest it.<\/p>\n\n\n\n
A clean and consistent URL structure is therefore better than contradictory signals between multiple versions of the same page.<\/p>\n\n\n\n
Does a subdomain need its own DNS records?<\/h2>\n\n\n\n
A subdomain must be able to be resolved accordingly via DNS.<\/p>\n\n\n\n
For this, an A, AAAA, or CNAME record can be used, for example.<\/p>\n\n\n\n
Which variant is correct depends on the desired target infrastructure.<\/p>\n\n\n\n
With the CURIAWEB DNS-Check<\/a> Can you check publicly visible DNS information?.<\/p>\n\n\n\n
Does a subdirectory need its own DNS record?<\/h2>\n\n\n\n
No.<\/p>\n\n\n\n
A URL path like<\/p>\n\n\n\n
example.ch\/blog\/<\/code><\/p>\n\n\n\n
is not controlled via a dedicated DNS record.<\/p>\n\n\n\n
DNS resolves the hostname example.ch<\/code> auf. Welcher Inhalt anschlie\u00dfend unter \/blog\/<\/code> ausgeliefert wird, entscheidet der Webserver beziehungsweise die darauf laufende Anwendung.<\/p>\n\n\n\n
Braucht eine Subdomain ein SSL-Zertifikat?<\/h2>\n\n\n\n
Wenn die Subdomain \u00fcber HTTPS erreichbar sein soll, muss sie von einem g\u00fcltigen SSL-\/TLS-Zertifikat abgedeckt sein.<\/p>\n\n\n\n
Ein Zertifikat, das nur f\u00fcr<\/p>\n\n\n\n
example.ch<\/code><\/p>\n\n\n\n
g\u00fcltig ist, deckt nicht automatisch<\/p>\n\n\n\n
blog.example.ch<\/code><\/p>\n\n\n\n
ab.<\/p>\n\n\n\n
Je nach Zertifikat k\u00f6nnen mehrere Hostnamen oder Subdomains enthalten sein. Auch Wildcard-Zertifikate k\u00f6nnen f\u00fcr bestimmte Subdomain-Konstellationen eingesetzt werden.<\/p>\n\n\n\n
Kann eine Subdomain eine eigene Search-Console-Property haben?<\/h2>\n\n\n\n
Ja. Abh\u00e4ngig vom verwendeten Property-Typ k\u00f6nnen Subdomains beziehungsweise URL-Pr\u00e4fixe in der Google Search Console separat betrachtet werden.<\/p>\n\n\n\n
Das kann bei gr\u00f6\u00dferen technisch getrennten Bereichen hilfreich sein.<\/p>\n\n\n\n
Eine Domain-Property kann dagegen Daten \u00fcber verschiedene Protokolle und Subdomains einer verifizierten Domain zusammenfassen.<\/p>\n\n\n\n
Kann Google Subdomains und Unterverzeichnisse unterschiedlich behandeln?<\/h2>\n\n\n\n
Ja, in bestimmten Google-Funktionen gibt es technische Unterschiede zwischen Hostnamen und Verzeichnissen.<\/p>\n\n\n\n
Beispielsweise definiert Google f\u00fcr einige Suchfunktionen eine Website auf Hostname-Ebene. Eine Subdomain kann dort deshalb separat behandelt werden, w\u00e4hrend ein Unterverzeichnis Bestandteil des bestehenden Hostnamens bleibt.<\/p>\n\n\n\n
Das sollte jedoch nicht mit einer allgemeinen Aussage \u00fcber Rankings verwechselt werden.<\/p>\n\n\n\n
\n
Important:<\/strong> Technische Unterschiede bei Hostnames, Search-Features oder Properties sind kein Beweis daf\u00fcr, dass Google Inhalte auf Subdomains grunds\u00e4tzlich schlechter rankt.<\/p>\n<\/blockquote>\n\n\n\n
Welche Variante ist einfacher zu verwalten?<\/h2>\n\n\n\n
Wenn s\u00e4mtliche Inhalte mit derselben Website beziehungsweise demselben CMS betrieben werden, ist ein Unterverzeichnis h\u00e4ufig einfacher.<\/p>\n\n\n\n
Es ben\u00f6tigt keine separate DNS-Zuordnung f\u00fcr den jeweiligen Bereich und l\u00e4sst sich meist unmittelbar in Navigation und URL-Struktur integrieren.<\/p>\n\n\n\n
Wenn unterschiedliche Anwendungen, Server oder Teams beteiligt sind, kann eine Subdomain dagegen eine sauberere technische Trennung erm\u00f6glichen.<\/p>\n\n\n\n
Welche Variante w\u00fcrden wir f\u00fcr normale Website-Inhalte w\u00e4hlen?<\/h2>\n\n\n\n
F\u00fcr Inhalte, die eindeutig Teil derselben Website sind \u2013 beispielsweise Blog, Ratgeber, Knowledgebase oder Leistungsinformationen \u2013 ist ein Unterverzeichnis h\u00e4ufig eine logische und wartungsfreundliche L\u00f6sung.<\/p>\n\n\n\n
F\u00fcr technisch eigenst\u00e4ndige Systeme wie Kundenportale, Webanwendungen, Entwicklungsumgebungen oder Statusseiten kann dagegen eine Subdomain sinnvoller sein.<\/p>\n\n\n\n
Das ist eine Architekturentscheidung und keine pauschale SEO-Regel.<\/p>\n\n\n\n
Welche Fragen sollte ich vor der Entscheidung beantworten?<\/h2>\n\n\n\n
Statt nur zu fragen \u201eWas ist besser f\u00fcr SEO?\u201c solltest du pr\u00fcfen, welche Rolle der neue Bereich tats\u00e4chlich erf\u00fcllt.<\/p>\n\n\n\n
Geh\u00f6rt der Inhalt fachlich und organisatorisch zur Hauptwebsite? Wird dasselbe CMS verwendet? Soll der Bereich dieselbe Navigation und Nutzerf\u00fchrung verwenden? Oder handelt es sich um eine technisch eigenst\u00e4ndige Anwendung, die unabh\u00e4ngig betrieben werden soll?<\/p>\n\n\n\n
Je st\u00e4rker ein Bereich mit der Hauptwebsite verbunden ist, desto nat\u00fcrlicher kann ein Unterverzeichnis sein. Je st\u00e4rker die technische Eigenst\u00e4ndigkeit im Vordergrund steht, desto sinnvoller kann eine Subdomain werden.<\/p>\n\n\n\n
Summary<\/h2>\n\n\n\n
Subdomains und Unterverzeichnisse sind zwei unterschiedliche M\u00f6glichkeiten, Inhalte und Dienste unter einer Domain zu strukturieren.<\/p>\n\n\n\n
A subdirectory like example.ch\/blog\/<\/code> bleibt Bestandteil desselben Hostnamens. Eine Subdomain wie blog.example.ch<\/code> ist dagegen ein eigener Hostname und kann technisch unabh\u00e4ngig auf einer anderen Infrastruktur betrieben werden.<\/p>\n\n\n\n
F\u00fcr SEO gibt es keine seri\u00f6se allgemeine Regel, nach der ein Unterverzeichnis automatisch besser rankt oder eine Subdomain grunds\u00e4tzlich schlechter w\u00e4re.<\/p>\n\n\n\n
F\u00fcr eng mit der Hauptwebsite verbundene Inhalte wie Blog, Ratgeber oder Knowledgebase ist ein Unterverzeichnis h\u00e4ufig eine einfache und logische Struktur. F\u00fcr technisch eigenst\u00e4ndige Anwendungen wie Kundenportale oder separate Systeme kann eine Subdomain die bessere Architektur darstellen.<\/p>\n\n\n\n
Wenn bereits eine funktionierende Struktur existiert, sollte sie nicht allein aufgrund vermeintlicher SEO-Vorteile ge\u00e4ndert werden. Ein Wechsel zwischen Subdomain und Unterverzeichnis ver\u00e4ndert URLs und muss als Migration mit korrekten Weiterleitungen und weiteren technischen Anpassungen behandelt werden.<\/p>\n\n\n\n
W\u00e4hle die Struktur deshalb nach Inhalt, Technik und langfristiger Wartbarkeit \u2013 nicht aufgrund des Mythos, dass Google eine der beiden Varianten grunds\u00e4tzlich bevorzugt.<\/strong><\/p>","protected":false},"excerpt":{"rendered":"
Wenn du einen neuen Bereich deiner Website aufbauen m\u00f6chtest, stellt sich h\u00e4ufig die Frage: Soll der Inhalt unter einer Subdomain oder in einem Unterverzeichnis liegen? Beide Varianten sind technisch m\u00f6glich und k\u00f6nnen von Suchmaschinen indexiert werden. Die Entscheidung sollte deshalb nicht auf der pauschalen Annahme beruhen, dass eine Subdomain oder ein Unterverzeichnis grunds\u00e4tzlich besser bei […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_joinchat":[],"footnotes":""},"doc_category":[82],"doc_tag":[],"class_list":["post-22789","docs","type-docs","status-publish","hentry","doc_category-domains-dns"],"year_month":"2026-09","word_count":2457,"total_views":"6","reactions":{"happy":"0","normal":"0","sad":"0"},"author_info":{"name":"Silvio Mazenauer","author_nicename":"admin-curia","author_url":"https:\/\/www.curiaweb.ch\/en\/author\/admin-curia\/"},"doc_category_info":[{"term_name":"Domains & DNS","term_url":"https:\/\/www.curiaweb.ch\/en\/hilfe-kategorie\/domains-dns\/"}],"doc_tag_info":[],"knowledge_base_info":[],"knowledge_base_slug":[],"_links":{"self":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22789","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/comments?post=22789"}],"version-history":[{"count":1,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22789\/revisions"}],"predecessor-version":[{"id":22791,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/docs\/22789\/revisions\/22791"}],"wp:attachment":[{"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/media?parent=22789"}],"wp:term":[{"taxonomy":"doc_category","embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/doc_category?post=22789"},{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/www.curiaweb.ch\/en\/wp-json\/wp\/v2\/doc_tag?post=22789"}],"curies":[{"name":"WP","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}