# Discussions Subdomains

I read in an article that Google finds it better if a page is not part of a subdomain. Which can contribute to a better ranking. This cannot now be substantiated with facts as to whether this is really the case. But I found the discussion about it interesting.

Let's think this through. A big company really shouldn't offer a site running under a subdomain that is part of a third party domain. In any case, in my opinion, this state of affairs paints the wrong picture. The first question that comes up would be, doesn't the company have enough money for a main domain?

This is an attitude that should be considered correct. However, this is only my opinion.

But now comes the big thing, I think subdomains are important and necessary. If a company offers internal services/portal. Which are not available to the public, then that's the way to go.

I could now create a subdomain under a Nextcloud is running. First of all, it would be an unknown service for third parties (bad people, I mean hackers). The domain would be unknown, since the service going through the reverse proxy cannot be resolved without the subdomain name.

## Benefits of a Subdomain

* So it's another hurdle and can be seen as a security feature.
* Subdomains are also easy to manage.
* Recognition is easier for users by grouping the main domain.

## Conclusion

It's one thing when we present something important, something for the public. I would totally understand Google along the way. But we can't do without it in the future either.

<figure><img src="https://1973811904-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Flk5l3lUfuUzRDnMDVwnw%2Fuploads%2FXQUxQp70SjLX1CyWpQw9%2F28pmaay4f9391.jpg?alt=media&#x26;token=edd557b6-213d-4b30-9f91-9ff4bae44fbc" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://flying-fish.gitbook.io/flyingfish/index/configurations/domains/discussions-subdomains.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.