A clearer path
from input to answer.
Every tool starts with your inputs. If you are unsure where to begin, use “Try an example” to see the expected format and a complete result. Then replace the example with your own values. The instructions, worked example and FAQs below each tool explain the choices that matter.
Choose the tool for the question
Start from the searchable directory or a topic collection. Margin, markup and contribution describe different relationships. A record checker inspects publication and syntax; a report reader summarizes supplied evidence. Read the tool’s introduction before treating two similar outputs as interchangeable.
Find a specific answer
The FAQ search combines the questions and answers from every tool. Search a tool name, input format or issue, then filter by category.
Compare business scenarios
Run a business calculator and use Save as A or Save as B to keep its headline results and inputs in this browser. Name each scenario, change an assumption and rerun to compare. Restore reloads the saved inputs and recalculates with the current tool. Reset clears the working form and results; Clear saved scenarios removes the saved pair for that tool. Keep currencies and periods consistent. Browser settings may restrict storage, in which case comparison lasts for the current visit.
Match units and time periods
Keep money amounts in one currency, without assuming that the tool converts exchange rates. Use the same reporting period for revenue, costs and balances where the formula requires it. Percent fields expect a percentage such as 20, rather than a decimal fraction such as 0.2, unless the input label says otherwise. Fields and result notes identify the supported units.
Prepare a file the tool can read
Use the example to inspect expected CSV columns and separators. Quoted commas and line breaks should remain inside their original cells. XML tools accept uncompressed XML and describe their encoding and size limits. JSON conversion expects the supported record structure. If a file has private information, make a small sanitized sample before investigating a formatting problem.
Review, copy and download
The result panel displays the relevant numbers or a preview of generated records. Some large outputs show only the first 500 rows while the download contains the full result. “Copy results” uses your browser’s clipboard support; downloads create local files. Review a compressed image before using it, and import a CSV with explicit text-column settings when leading zeroes matter.
If a result does not appear
Check the error message beside the form. Missing required values, a zero denominator, unsupported file syntax or a size limit can stop processing. Enable JavaScript and use a current browser for these client-side tools. Reset restores the original form values and clears results. Live DNS checks also need a successful network connection to Google Public DNS; a timeout is not an authentication pass.
Understand the scope of a warning
Some tools identify a pattern to investigate rather than an error to fix automatically. Two pages appearing for one search query do not by themselves prove a targeting problem. An approximate metadata-length flag is not a Google character limit. Read the result notes and the source references before changing a site, email record or business policy.
Report a reproducible issue
When requesting a correction from the site owner, include the tool name, selected mode, browser, small sanitized inputs, expected result and actual result. Explain whether the issue happens with the built-in example too. That separates a calculation problem from a file-format or input-selection problem. Use the corrections form to prepare and email a report. A response time is not guaranteed.
Data handling and methods
Most tools process inputs locally. Live DNS modes disclose the external query separately. See privacy and data for the current behavior and editorial standards for how sources, examples and assumptions are documented.