Question 1

Will this affect my existing website?

Accepted Answer

No. The proxy only handles specific paths you define. Your existing pages, routes, and functionality remain completely untouched. If a path isn't in your rewrite configuration, it works exactly as before.

Question 2

Can search engines see my content properly?

Accepted Answer

Yes. Search engines see the content as coming from your domain. We include proper canonical URLs, meta tags, and Open Graph tags pointing to your domain. From Google's perspective, the content lives at yourdomain.com/page, not on our servers.

Question 3

How fast are proxied pages?

Accepted Answer

The proxy adds minimal latency (typically 50-150ms). Pages are pre-rendered as static HTML, cached at edge servers worldwide, and cached by your hosting platform. After the first request, subsequent visitors often get cached responses with no additional latency.

Question 4

What happens if Nexting goes down?

Accepted Answer

If our servers are unavailable, proxied pages will return errors. However, your main website continues to work normally since non-proxied paths aren't affected. We maintain high availability with redundant infrastructure.

Question 5

Can I use custom CSS or JavaScript?

Accepted Answer

Currently, pages use our default styling optimized for readability and SEO. Custom styling options are on our roadmap. You can include inline styles in your HTML content.

Question 6

How do I update content?

Accepted Answer

Edit the page in your Nexting dashboard and save. Changes propagate within 5 minutes due to caching. No deployment or code changes required.

Question 7

Is there a limit on pages?

Accepted Answer

Free accounts can create up to 10 pages per project. Paid plans offer unlimited pages. Check our pricing page for details.

Question 8

Can I use my own domain for the API?

Accepted Answer

The standard setup uses our API domain for the proxy destination. Enterprise plans can use custom API domains for white-labeling.

Question 9

Is the project key secret?

Accepted Answer

The project key is semi-public — it appears in your configuration files which may be in version control. However, it only provides read access to published pages, cannot be used to modify content, and doesn't expose any private data. Think of it like a public API key — safe to include in frontend code.

Question 10

Can multiple domains use the same project?

Accepted Answer

Each project is tied to one primary domain. If you need the same content on multiple domains, create separate projects and link them to the same content source (coming soon), or duplicate the pages.

Frequently Asked Questions

Have another question?