{"id":141,"date":"2026-08-17T19:52:50","date_gmt":"2026-08-17T12:52:50","guid":{"rendered":"https:\/\/bkmos.com\/en\/?p=141"},"modified":"2026-08-17T19:52:50","modified_gmt":"2026-08-17T12:52:50","slug":"how-to-evaluate-translation-provider","status":"publish","type":"post","link":"https:\/\/bkmos.com\/en\/blog\/how-to-evaluate-translation-provider\/","title":{"rendered":"How to Evaluate a Translation Provider: A Practical Buyer\u2019s Guide"},"content":{"rendered":"
\n

<\/p>\n

\n
\n<\/p>\n\n\n
<\/p>\n


\n CHOOSING A TRANSLATION PROVIDER
\n <\/span><\/p>\n


\n Choosing a translation provider is not only about comparing
\n price per word. The right partner should be able to understand
\n your content, assign suitable linguists, protect confidential
\n information, manage terminology, control quality and deliver
\n reliably at the scale your organization requires.\n <\/p>\n


\n A strong evaluation process therefore looks at expertise,
\n workflow, security, technology, communication and long-term
\n value rather than relying on one sales claim or a single low quote.\n <\/p>\n<\/td>\n

<\/p>\n
<\/p>\n

\"How<\/p>\n<\/figure>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

\n

\n The best provider for a certified personal document may not be the same
\n provider best suited to a multilingual technical manual, software
\n localization program or recurring financial-reporting workflow.\n <\/p>\n

\n This guide provides a practical framework for comparing translation
\n companies before assigning an important project or building a long-term relationship.\n <\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n QUICK OVERVIEW<\/span><\/p>\n

What Should You Evaluate First?<\/h2>\n<\/p><\/div>\n
\n
\n 01<\/span><\/p>\n

Relevant Expertise<\/h3>\n

\n Look for experience with your content type, subject matter,
\n language pair and intended use.\n <\/p>\n<\/article>\n

\n 02<\/span><\/p>\n

Quality Process<\/h3>\n

\n Ask how translation, review, terminology control and final QA
\n are organized for your project.\n <\/p>\n<\/article>\n

\n 03<\/span><\/p>\n

Security & Reliability<\/h3>\n

\n Confirm confidentiality, access control, project ownership,
\n turnaround and escalation procedures.\n <\/p>\n<\/article>\n

\n 04<\/span><\/p>\n

Value, Not Just Price<\/h3>\n

\n Compare what each quote actually includes and whether the workflow
\n matches the risk and importance of your content.\n <\/p>\n<\/article><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n
\n STEP 1 \u2014 DEFINE THE PROJECT<\/span><\/p>\n

Know What You Need Before Comparing Providers<\/h2>\n

\n Translation providers cannot be evaluated fairly if the project
\n requirements are vague. Start by identifying the languages,
\n content type, volume, file formats, deadline and intended use.\n <\/p>\n

\n Also consider whether the project needs certification, specialist
\n review, multilingual DTP, terminology management, confidentiality
\n controls or recurring updates.\n <\/p>\n

\n A clear scope makes quotations easier to compare and reduces the
\n risk of selecting a provider whose service model does not fit the project.\n <\/p>\n<\/p><\/div>\n

\n
\n

Languages<\/h3>\n

Identify source and target languages, including any target-market variants.<\/p>\n<\/p><\/div>\n

\n

Content Type<\/h3>\n

Legal, technical, medical, financial, academic, marketing or general content.<\/p>\n<\/p><\/div>\n

\n

Volume & Deadline<\/h3>\n

Provide realistic page, word or file volume together with the required delivery date.<\/p>\n<\/p><\/div>\n

\n

Final Use<\/h3>\n

Internal review, publication, submission, certification, localization or another purpose.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n SUBJECT-MATTER EXPERTISE<\/span><\/p>\n

Relevant Experience Matters More Than Generic Claims<\/h2>\n

\n A provider may work in many languages but still lack the specialist
\n knowledge needed for a particular document type or industry.\n <\/p>\n<\/p><\/div>\n

\n
\n Legal<\/strong><\/p>\n

Contracts, litigation, corporate records and formal legal documentation.<\/p>\n<\/p><\/div>\n

\n Technical<\/strong><\/p>\n

Manuals, SOPs, engineering specifications, drawings and manufacturing content.<\/p>\n<\/p><\/div>\n

\n Medical<\/strong><\/p>\n

Medical records, clinical terminology, laboratory results and healthcare documents.<\/p>\n<\/p><\/div>\n

\n Financial<\/strong><\/p>\n

Financial statements, audit materials, banking and business-reporting content.<\/p>\n<\/p><\/div>\n

\n Academic<\/strong><\/p>\n

Transcripts, diplomas, certificates and study-abroad documentation.<\/p>\n<\/p><\/div>\n

\n Localization<\/strong><\/p>\n

Websites, apps, software, e-commerce and multilingual digital content.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n
\n LINGUIST SELECTION<\/span><\/p>\n

Ask Who Will Actually Translate Your Content<\/h2>\n

\n The quality of a translation ultimately depends on the people assigned
\n to the project. Ask how translators and reviewers are selected for
\n the language pair and subject matter.\n <\/p>\n

\n For specialist content, language ability alone may not be enough.
\n The linguist should understand the terminology, document conventions
\n and risk level of the field.\n <\/p>\n

\n Large providers may have broad networks, while smaller providers may
\n offer more direct control over individual linguist selection.
\n The important point is whether the assignment process is suitable for your project.\n <\/p>\n<\/p><\/div>\n

\n
\n

Language Competence<\/h3>\n

Confirm professional command of both source and target languages.<\/p>\n<\/p><\/div>\n

\n

Subject Knowledge<\/h3>\n

Check whether the translator has relevant industry or document experience.<\/p>\n<\/p><\/div>\n

\n

Target-Language Writing<\/h3>\n

The final text should be natural and appropriate for the intended audience.<\/p>\n<\/p><\/div>\n

\n

Reviewer Fit<\/h3>\n

Where review is included, the reviewer should also match the project’s language and subject needs.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n<\/p>\n\n\n
<\/p>\n

QUALITY ASSURANCE<\/span><\/p>\n

\n Ask for the Workflow, Not Just the Phrase \u201cHigh Quality\u201d
\n <\/h2>\n

\n Nearly every provider describes its work as high quality.
\n A more useful question is how quality is actually produced
\n and checked during the project.\n <\/p>\n

\n Depending on the project, this may include translator self-review,
\n independent revision, terminology management, numerical checks,
\n layout QA and final file verification.\n <\/p>\n

\n The process should match the risk of the content.
\n A short internal email and a court filing do not necessarily
\n require the same level of review.\n <\/p>\n


\n ABOUT BKMOS
\n <\/a><\/p>\n<\/td>\n

<\/p>\n
\n
\n Translation \u2192 Qualified linguist<\/strong>\n <\/div>\n
\n Revision \u2192 Second-person review where required<\/strong>\n <\/div>\n
\n Terminology \u2192 Project glossary \/ approved references<\/strong>\n <\/div>\n
\n QA \u2192 Names, numbers, formatting and completeness<\/strong>\n <\/div>\n
\n Final delivery \u2192 File and version check<\/strong>\n <\/div>\n<\/p><\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n
\n TERMINOLOGY & CONSISTENCY<\/span><\/p>\n

Ask How the Provider Controls Repeated Language<\/h2>\n

\n Terminology becomes especially important in large or recurring projects.
\n The same product, component, account, legal term or feature should not
\n be translated differently from file to file without a reason.\n <\/p>\n

\n A provider should be able to explain how client glossaries,
\n previous approved translations and project-specific terminology
\n are stored and applied.\n <\/p>\n

\n This is particularly valuable when several translators work on the
\n same program or when new content is translated over many months or years.\n <\/p>\n<\/p><\/div>\n

\n
\n

Glossary<\/h3>\n

Approved terminology for recurring high-value terms.<\/p>\n<\/p><\/div>\n

\n

Style Guide<\/h3>\n

Rules for tone, capitalization, punctuation, brand voice and formatting.<\/p>\n<\/p><\/div>\n

\n

Previous Translations<\/h3>\n

Reuse approved wording where consistency with earlier documents matters.<\/p>\n<\/p><\/div>\n

\n

Client Feedback<\/h3>\n

Record approved corrections so the same issue does not repeat in later projects.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n
\n SECURITY & CONFIDENTIALITY<\/span><\/p>\n

Understand How Your Files Will Be Handled<\/h2>\n

\n Translation projects can contain personal data, contracts,
\n financial information, medical records, product designs
\n and other sensitive business information.\n <\/p>\n

\n Ask who can access your files, how they are transferred,
\n whether subcontractors are used and what confidentiality
\n requirements apply to translators and project staff.\n <\/p>\n

\n If your organization requires an NDA, specific data handling
\n or retention terms, raise those requirements before work begins.\n <\/p>\n<\/p><\/div>\n

\n
\n

NDA<\/h3>\n

Confirm whether confidentiality agreements can be executed when required.<\/p>\n<\/p><\/div>\n

\n

File Transfer<\/h3>\n

Understand how source and translated files move between parties.<\/p>\n<\/p><\/div>\n

\n

Access Control<\/h3>\n

Ask which people or systems can access confidential project material.<\/p>\n<\/p><\/div>\n

\n

Retention<\/h3>\n

Confirm project-specific retention or deletion requirements where relevant.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n
\n TRANSLATION TECHNOLOGY<\/span><\/p>\n

Technology Should Support Quality and Efficiency \u2014 Not Replace Project Judgment<\/h2>\n

\n Translation memory, terminology tools and automated QA can improve
\n consistency and reduce repeated work in suitable projects.\n <\/p>\n

\n For websites, software and large content programs, integration with
\n content systems or localization platforms can also reduce manual file handling.\n <\/p>\n

\n Ask what tools will be used, how client data is handled and how
\n technology fits into the human translation and review workflow.\n <\/p>\n<\/p><\/div>\n

\n
\n

Translation Memory<\/h3>\n

Reuse approved translated segments where appropriate.<\/p>\n<\/p><\/div>\n

\n

Terminology Tools<\/h3>\n

Support consistent application of project glossaries.<\/p>\n<\/p><\/div>\n

\n

Automated QA<\/h3>\n

Check selected issues such as numbers, terminology and missing content.<\/p>\n<\/p><\/div>\n

\n

Integration<\/h3>\n

Useful for recurring website, app and content-management workflows.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n PROJECT MANAGEMENT<\/span><\/p>\n

Communication Quality Is Part of Translation Quality<\/h2>\n<\/p><\/div>\n
\n
\n Single Contact<\/strong><\/p>\n

A clear project owner reduces confusion and keeps decisions centralized.<\/p>\n<\/p><\/div>\n

\n Scope Confirmation<\/strong><\/p>\n

Files, languages, services, deadline and deliverables should be agreed before work starts.<\/p>\n<\/p><\/div>\n

\n Questions<\/strong><\/p>\n

The provider should have a practical way to raise source-text and terminology questions.<\/p>\n<\/p><\/div>\n

\n Status Updates<\/strong><\/p>\n

Large or urgent projects benefit from clear progress communication.<\/p>\n<\/p><\/div>\n

\n Change Control<\/strong><\/p>\n

Revised source files and additional scope should be tracked clearly.<\/p>\n<\/p><\/div>\n

\n Escalation<\/strong><\/p>\n

Know who handles urgent quality, schedule or commercial issues.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n
\n PRICING & VALUE<\/span><\/p>\n

Compare Scope Before Comparing Price<\/h2>\n

\n Two quotations can show different prices because they include
\n different levels of review, formatting, project management,
\n certification or technical handling.\n <\/p>\n

\n A low price is not automatically poor value, and a high price is
\n not automatically high quality. The important question is whether
\n the quoted workflow is appropriate for the project and clearly defined.\n <\/p>\n

\n Ask about minimum charges, rush fees, DTP, certification,
\n revisions and any other costs that may apply before approving the project.\n <\/p>\n<\/p><\/div>\n

\n
Translation \u2192 Included?<\/strong><\/div>\n
Independent review \u2192 Included or optional?<\/strong><\/div>\n
DTP \/ formatting \u2192 Included or separate?<\/strong><\/div>\n
Certification \u2192 Included or separate?<\/strong><\/div>\n
Rush delivery \u2192 Additional charge?<\/strong><\/div>\n
Revisions \u2192 What is covered?<\/strong><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n
\n TESTING A PROVIDER<\/span><\/p>\n

For Large Programs, a Representative Test Can Be More Useful Than a Generic Sample<\/h2>\n

\n Published samples can show writing quality, but they may not reflect
\n the people or workflow that will be assigned to your project.\n <\/p>\n

\n For a large recurring program, a small paid pilot using representative
\n content can provide better evidence of terminology handling, communication,
\n turnaround and review quality.\n <\/p>\n

\n The test should resemble the real project closely enough to produce useful findings.\n <\/p>\n<\/p><\/div>\n

\n
\n

Representative Content<\/h3>\n

Choose material that reflects the terminology and difficulty of the real project.<\/p>\n<\/p><\/div>\n

\n

Same Workflow<\/h3>\n

Use the review and QA process proposed for the full program.<\/p>\n<\/p><\/div>\n

\n

Clear Evaluation<\/h3>\n

Review accuracy, fluency, terminology, questions, turnaround and formatting.<\/p>\n<\/p><\/div>\n

\n

Document Feedback<\/h3>\n

Record approved terminology and style decisions for future work.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n<\/p>\n\n\n
<\/p>\n

RED FLAGS<\/span><\/p>\n

\n Warning Signs to Investigate Before Awarding the Project
\n <\/h2>\n

\n No single warning sign proves that a provider is unsuitable,
\n but several unresolved issues should prompt additional questions.\n <\/p>\n

\n Be cautious when a supplier promises unrealistic turnaround,
\n cannot explain its quality workflow or provides a quote without
\n reviewing important project requirements.\n <\/p>\n

\n A reliable provider should be willing to explain assumptions,
\n limitations and what it needs from the client to deliver the project well.\n <\/p>\n


\n DISCUSS YOUR PROJECT
\n <\/a><\/p>\n<\/td>\n

<\/p>\n
\n
\n Unrealistic deadline with no scope discussion<\/strong>\n <\/div>\n
\n No clear explanation of translator or reviewer selection<\/strong>\n <\/div>\n
\n No defined quality or revision process<\/strong>\n <\/div>\n
\n Unclear confidentiality or file handling<\/strong>\n <\/div>\n
\n Poor communication before the project even begins<\/strong>\n <\/div>\n
\n Pricing that cannot be reconciled with the promised scope<\/strong>\n <\/div>\n<\/p><\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n COMPARISON SCORECARD<\/span><\/p>\n

A Simple Framework for Shortlisting Providers<\/h2>\n

\n Weight the criteria according to your project rather than treating
\n every category as equally important.\n <\/p>\n<\/p><\/div>\n

\n
\n Expertise<\/strong><\/p>\n

Does the provider understand the language pair, document type and subject?<\/p>\n<\/p><\/div>\n

\n Quality Process<\/strong><\/p>\n

Is the proposed review workflow clear and appropriate to the risk?<\/p>\n<\/p><\/div>\n

\n Security<\/strong><\/p>\n

Can the provider meet your confidentiality and file-handling requirements?<\/p>\n<\/p><\/div>\n

\n Project Management<\/strong><\/p>\n

Are communication, turnaround and change control clearly defined?<\/p>\n<\/p><\/div>\n

\n Technology<\/strong><\/p>\n

Are the tools appropriate for terminology, file formats and recurring work?<\/p>\n<\/p><\/div>\n

\n Commercial Fit<\/strong><\/p>\n

Does the quote provide suitable value for the proposed scope and service level?<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n SELECTION PROCESS<\/span><\/p>\n

A Practical Translation Provider Evaluation Workflow<\/h2>\n<\/p><\/div>\n
\n
\n 1<\/span><\/p>\n

Define Requirements<\/h3>\n

Clarify languages, content, volume, intended use, deadline and service level.<\/p>\n<\/p><\/div>\n

\n 2<\/span><\/p>\n

Shortlist Providers<\/h3>\n

Compare relevant experience, workflows, security and project capabilities.<\/p>\n<\/p><\/div>\n

\n 3<\/span><\/p>\n

Evaluate Proposal<\/h3>\n

Review scope, assumptions, quality steps, communication and total cost.<\/p>\n<\/p><\/div>\n

\n 4<\/span><\/p>\n

Pilot & Onboard<\/h3>\n

For larger programs, validate the workflow and then document approved terminology and processes.<\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n
\n BUYER CHECKLIST<\/span><\/p>\n

Questions to Ask Before Choosing a Translation Provider<\/h2>\n

\n Use this checklist to compare suppliers against the needs of
\n your actual project rather than generic marketing claims.\n <\/p>\n


\n REQUEST A BKMOS QUOTE
\n <\/a>\n <\/div>\n

\n
\u2713 Who will translate and review the content?<\/strong><\/div>\n
\u2713 What relevant subject-matter experience do they have?<\/strong><\/div>\n
\u2713 What QA steps are included?<\/strong><\/div>\n
\u2713 How is terminology managed?<\/strong><\/div>\n
\u2713 How are confidential files handled?<\/strong><\/div>\n
\u2713 What tools and file formats are supported?<\/strong><\/div>\n
\u2713 Who owns project communication and escalation?<\/strong><\/div>\n
\u2713 What exactly is included in the quoted price?<\/strong><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n RELATED RESOURCES<\/span><\/p>\n

Explore BKMOS Translation Services<\/h2>\n<\/p><\/div>\n
\n
\n Specialized Translation<\/strong><\/p>\n

\n Technical, medical, financial, legal and other
\n subject-specific translation services.\n <\/p>\n


\n Specialized Translation \u2192
\n <\/a>\n <\/div>\n

\n Certified & Notarized Translation<\/strong><\/p>\n

\n Translation and formal processing support for
\n documents requiring certification.\n <\/p>\n


\n Certified Translation \u2192
\n <\/a>\n <\/div>\n

\n Translation Rates<\/strong><\/p>\n

\n Review BKMOS pricing information and factors
\n that can affect translation project cost.\n <\/p>\n


\n Translation Rates \u2192
\n <\/a>\n <\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n FREQUENTLY ASKED QUESTIONS<\/span><\/p>\n

Translation Provider Evaluation FAQs<\/h2>\n<\/p><\/div>\n
\n
\n

Should I choose the translation provider with the lowest price?<\/h3>\n

\n Not automatically. Compare what each quote includes, the proposed quality
\n workflow and whether the provider has suitable experience for the content.\n <\/p>\n<\/p><\/div>\n

\n

How important is subject-matter experience?<\/h3>\n

\n It can be critical for legal, technical, medical, financial and other
\n specialist content where terminology and document conventions affect meaning.\n <\/p>\n<\/p><\/div>\n

\n

Should I ask for a free translation test?<\/h3>\n

\n For major programs, a representative paid pilot may provide more useful
\n evidence because it can use the real proposed workflow and project conditions.\n <\/p>\n<\/p><\/div>\n

\n

What should a translation quality process include?<\/h3>\n

\n It depends on the project, but may include translator review, independent
\n revision, terminology checks, numerical QA, formatting review and final file verification.\n <\/p>\n<\/p><\/div>\n

\n

Why does confidentiality matter when choosing a provider?<\/h3>\n

\n Translation files may contain sensitive personal, legal, financial,
\n medical or business information, so access and file handling should be understood in advance.\n <\/p>\n<\/p><\/div>\n

\n

What should I send when requesting a quotation?<\/h3>\n

\n Send representative files, the source and target languages, intended use,
\n required output format, deadline and any known certification or confidentiality requirements.\n <\/p>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n

EXPERT REVIEW<\/span><\/p>\n

Reviewed by Nguyen Dinh Phuc<\/h2>\n

\n Founder & CEO of BKMOS. Working in professional translation
\n since 2005 and responsible for BKMOS’s professional direction,
\n translation workflows and expert content.\n <\/p>\n


\n About BKMOS \u2192
\n <\/a><\/p><\/div>\n<\/p><\/div>\n<\/section>\n

<\/p>\n

\n
\n
\n
\n CHOOSING A TRANSLATION PARTNER<\/span><\/p>\n

Need to Evaluate BKMOS for Your Translation Project?<\/h2>\n

\n Send BKMOS representative files together with the language pair,
\n intended use, required services and deadline. We can review the
\n project requirements and provide a quotation based on the actual scope.\n <\/p>\n<\/p><\/div>\n

\n
\n REQUEST A PROJECT QUOTE
\n <\/a>\n <\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/section>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

CHOOSING A TRANSLATION PROVIDER Choosing a translation provider is not only about comparing price per word. The right partner should be able to understand your content, assign suitable linguists, protect confidential information, manage terminology, control quality and deliver reliably at the scale your organization requires. A strong evaluation process therefore looks at expertise, workflow, security, […]\n","protected":false},"author":1,"featured_media":142,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10],"tags":[],"class_list":["post-141","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-translation-resources-buying-guides"],"_links":{"self":[{"href":"https:\/\/bkmos.com\/en\/wp-json\/wp\/v2\/posts\/141","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bkmos.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/bkmos.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/bkmos.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/bkmos.com\/en\/wp-json\/wp\/v2\/comments?post=141"}],"version-history":[{"count":1,"href":"https:\/\/bkmos.com\/en\/wp-json\/wp\/v2\/posts\/141\/revisions"}],"predecessor-version":[{"id":143,"href":"https:\/\/bkmos.com\/en\/wp-json\/wp\/v2\/posts\/141\/revisions\/143"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/bkmos.com\/en\/wp-json\/wp\/v2\/media\/142"}],"wp:attachment":[{"href":"https:\/\/bkmos.com\/en\/wp-json\/wp\/v2\/media?parent=141"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bkmos.com\/en\/wp-json\/wp\/v2\/categories?post=141"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bkmos.com\/en\/wp-json\/wp\/v2\/tags?post=141"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}