Start with the category that matches your problem. Each answer is written to reduce guesswork, speed up self-service, and keep support requests focused when escalation is actually needed.
What OKO Tools is, who it is for, and how to get value fast.
Getting started
What OKO Tools is, who it is for, and how to get value fast.
What is OKO Tools?
OKO Tools lets you describe one narrow use case and turn it into one simple online tool page. Each page can include inputs, a result, a guide, examples, and FAQ without building a full app.
What is the fastest way to get value from the product?
Start with one narrow use case. Avoid broad platforms, multi-step workflows, or admin-heavy prompts. The product works best when the prompt describes one focused calculator, helper, or decision page.
Open the builder.
Write one narrow prompt, ideally one output and one market.
Generate the first draft.
Verify it, fix issues if needed, then save or publish.
Do not start from the full business idea. Start from one user question. If you can finish the sentence 'I want to calculate...' or 'I want to compare...', the builder usually has enough scope to make a useful first draft.
Write the user question in one line.
Reduce it to one calculation or one decision output.
Add market or country only if rules differ.
Generate the first tool and refine from there.
What kinds of tools work best?
The best fits are one-screen tools such as salary, loan, ROI, fuel, import, budget, comparison, planning, or construction helpers. The system is optimized for one clear result and one clear next step.
How to write prompts, refine drafts, edit sections, and fix weak generations.
Builder and generation
How to write prompts, refine drafts, edit sections, and fix weak generations.
How should I write a good prompt?
Use plain language. Name the tool, the outcome, and the market only if it matters. The cleaner the scope, the better the first draft.
Start with the tool type: calculator, helper, planner, comparison tool.
Add the output you want: monthly payment, tax after salary, ROI, quote estimate.
Add market only if rules differ by country or region.
Avoid asking for dashboards, workflows, admin panels, or full apps.
Can I keep refining after the first draft?
Yes. After generation, the builder switches into refine mode. Use the prompt again only for a stronger rebuild. For small fixes, use the editor or click directly on a section in the preview.
What do Verify, Auto-fix, Save draft, and Publish mean?
These are the main builder actions and they work best in one simple order.
Verify checks trust, quality, formula, and publishing issues.
Auto-fix attempts to repair obvious problems in the draft.
Save draft stores the current version in your workspace.
Publish sends the page live or into review, depending on readiness.
What does Open editor do?
Open editor gives you quick access to the main editable parts of the page. It is meant for targeted changes, not for rebuilding the whole tool from scratch.
Can I import from an existing page?
Yes. The builder supports import from URL as a starting point for one focused helper. It is designed to extract structure and propose a draft, not clone full apps or workflows.
How do I fix a draft that looks too broad or confusing?
Broad drafts usually come from broad prompts. The fastest fix is to rebuild with a narrower sentence instead of trying to patch every section manually.
Remove platform or workflow language.
Keep only one tool purpose and one main result.
Name the market only if it changes logic.
Run Verify again after the rebuild.
What should I do if Examples or FAQ look weak?
Treat them as support content, not filler. Examples should reflect realistic input scenarios. FAQ should answer obvious questions a real user will ask before trusting the result.
Use examples with concrete values.
Avoid repeating the title in every answer.
Write questions about trust, scope, assumptions, and interpretation.
Keep examples and FAQ shorter than the main guide.
Publishing and review
How drafts move into review, live pages, and public discovery.
Publishing and review
How drafts move into review, live pages, and public discovery.
Why does Publish sometimes send the tool to review instead of making it live?
A tool only goes live immediately if it is fully ready. Otherwise the publish action sends it into review. This keeps the public directory cleaner and reduces thin or misleading pages.
What do Needs fixes, Needs review, and Live-ready mean?
These statuses describe where the draft stands right now. Needs fixes means something still blocks publishing. Needs review means the draft can move into the review lane. Live-ready means it is ready to go live.
Why was my tool not visible on the public page right away?
If the draft is in review or changes-requested, the public route stays unavailable. Only approved public tools are shown on /tools/[slug], the directory, and related discovery surfaces.
How focused market-specific tools fit into discovery, trust, and SEO.
Geo and niche tools
How focused market-specific tools fit into discovery, trust, and SEO.
Why do geo and niche tools matter?
These pages target narrow practical intent such as Sweden salary, USA mortgage, UK rental yield, Airbnb ROI, or Sweden car import. They are usually easier to rank, easier to explain, and easier to trust than generic catch-all pages.
Keep one market or one narrow use case per page.
Use realistic examples for that market.
Keep FAQ specific to the local question behind the calculator.
Link to adjacent tools in the same cluster instead of broad unrelated pages.
Expand sideways, not randomly. Build adjacent pages that answer the next obvious question in the same market or niche instead of jumping into unrelated categories.
Start from one live page with real usage.
Check related searches and repeat questions from support or analytics.
Create one adjacent page that shares the same trust context.
Link the pages together through related tools and FAQ guidance.
Which newer geo and niche pages should I connect first?
Start with the newest live waves that already sit close to clear user intent. Those pages should be linked from FAQ, support, result loops, and adjacent tool pages before you expand further.
Connect the newest salary pages to the older Sweden salary pages.
Connect the newest mortgage pages to the existing USA payment, affordability, and refinance tools.
Connect the newest import pages to the closest country-specific import screens.
Connect the newest Airbnb pages to ROI, nightly-rate, occupancy, and break-even tools.
What is the best next layer after one live geo page starts working?
Add one adjacent page that answers the next obvious question in the same market or niche. Good examples are Sweden salary to Sweden hourly pay, USA mortgage payment to USA refinance savings, or Airbnb ROI to Airbnb nightly-rate target.
Look at the current result page and ask what the next practical question is.
Build that adjacent page before you branch into a different market.
Reuse the same examples, trust framing, and FAQ language where possible.
Link the cluster through the tool page, result page, FAQ, and directory intent search.
Which adjacent pages should I add after the current geo and niche cluster starts getting traffic?
Stay inside the same decision path. For salary, add yearly-net variants after monthly and hourly pages. For mortgages, add DTI and closing-cost pages after payment and affordability. For imports, add market-specific car-import pages after general landed-cost pages. For Airbnb, add revenue and cleaning-pressure pages after ROI and nightly-rate tools.
Look for the next obvious question after the first result.
Add only one adjacent page inside the same market or hosting/import path.
Reuse the same examples and trust framing where possible.
Link the pages through tool pages, results, FAQ, and support flows.
Login, password reset, sessions, and account protection.
Accounts and security
Login, password reset, sessions, and account protection.
Do I need an account?
Yes, for saving drafts, publishing tools, managing your profile, or using the full workspace. Public pages and the directory can still be browsed without signing in.
Password reset works through email. You request a reset link, open the email, choose a new password, and the account is signed back in with fresh sessions.
Open the email reset page.
Enter your account email.
Open the message from no-reply@mail.oko360.online.
How do I fix Something went wrong on a workspace page?
That error usually comes from stale session state, stale cached assets, or a failed request during page load. The fix is usually operational, not account deletion or re-registration.
Reload the page once.
If you use the PWA, hard refresh or reopen the app.
Sign out and sign back in.
If the issue persists, send the exact page URL and action to support.
Public pages and results
How tool pages, shared results, collections, and discovery work.
Public pages and results
How tool pages, shared results, collections, and discovery work.
What is the difference between a tool page and a result page?
A tool page is the main live calculator or helper. A result page is a saved output from a specific run of that tool. Result pages are meant for replay, comparison, or sharing one concrete outcome.
Why do examples and FAQ exist on a tool page?
They help users understand the tool quickly, see realistic scenarios, and get answers without leaving the page. They also improve usefulness and search visibility when written clearly.
Why do some links show only live tools?
Public discovery surfaces are intentionally filtered to approved live tools. Drafts, review-stage tools, and archived items are kept out of public browsing to avoid confusion and broken routes.
Yes. Shared result pages let users send one concrete result to someone else, then reopen the original tool or continue with the same scenario.
How do I fix a result page that points to an unavailable tool?
If a tool is archived or not live anymore, shared result pages should be treated as result records, not as proof that the original public tool is still available. The correct next step is to browse live tools or reopen a current draft.
How quality checks work and why some pages are blocked or reviewed.
Quality, trust, and moderation
How quality checks work and why some pages are blocked or reviewed.
Why is thin content a problem?
Thin content weakens trust, hurts search quality, and creates low-value public pages. Public tools should explain what they do, show useful scenarios, and answer obvious questions clearly.
Why does duplicate risk matter?
Too many near-identical tools split trust, traffic, and maintenance. If a stronger root tool already exists, improving that version is usually better than creating another overlapping page.
What does Use with context mean on tool pages?
That section explains scope, status, assumptions, release state, and trust posture without getting in the way of the first calculation screen.
Where can I learn the publication rules?
Use the creator guidelines, support page, privacy policy, and terms if you need the full product, moderation, or policy explanation.
Do not add more copy just to look longer. Make the page more useful. Remove repetitive keywords, remove promotional lines, explain the result clearly, and add realistic examples or better FAQ.
Cut repeated keywords and sales wording.
Remove links, contact details, and promotional promises.
Add one clear guide section with practical explanation.
Use realistic examples and concise FAQ.
Creators, admin, and operations
How creators, reviewers, and operators should work without creating workflow debt.
Creators, admin, and operations
How creators, reviewers, and operators should work without creating workflow debt.
What should creators do before sending a page to review?
Creators should treat review as a quality gate, not as a cleanup service. A draft should already have a valid formula, useful copy, realistic examples, and clear scope before entering review.
Verify the draft.
Fix formula or trust issues.
Make sure the title, inputs, guide, examples, and FAQ are coherent.
Review should focus on clarity, trust, and public usefulness. If a page would confuse real users, send it back with one clear note instead of approving a weak version.
Check if the page is truly one-screen and one-purpose.
Check if the result is understandable without internal context.
Reject repeated or spam-like copy.
Leave one concrete change note that the creator can act on.
Ops is for incidents, backups, restore health, runtime flags, and operational state. Support is for user-facing help, access problems, and bug reports. Do not mix those lanes unless the issue is clearly operational.
Do not just approve items to clear the queue. Clear duplicate drafts, archive dead pages, push weak pages back with notes, and only approve tools that are safe to keep live.
Claim the page if you are handling it.
Decide: approve, send back, or archive.
Leave a useful note when sending back changes.
Use releases and dashboard to confirm the public/live state after actions.
Mobile, PWA, and support
How the mobile version works and where to ask for help.
Mobile, PWA, and support
How the mobile version works and where to ask for help.
Does OKO Tools work as a mobile web app?
Yes. The product supports mobile and PWA behavior, including a manifest, service worker, and responsive layouts for builder, tool pages, results, auth, and directory flows.
What should I do if something looks broken on mobile?
First do a hard refresh. If the issue persists, report the exact page, device, and action that failed. For PWA cache issues, updating or reinstalling the app view can also help.
