{"id":25236,"date":"2026-03-18T13:31:02","date_gmt":"2026-03-18T08:01:02","guid":{"rendered":"https:\/\/empmonitor.com\/blog\/?p=25236"},"modified":"2026-03-18T13:31:02","modified_gmt":"2026-03-18T08:01:02","slug":"how-empmonitor-transformed-remote-team","status":"publish","type":"post","link":"https:\/\/empmonitor.com\/blog\/how-empmonitor-transformed-remote-team\/","title":{"rendered":"What Happened After We Implemented EmpMonitor Across Our Remote Team"},"content":{"rendered":"<p style=\"text-align: justify\"><i><span style=\"font-weight: 400\">A first-person account of what actually changed, in productivity, accountability, and team morale, after rolling out EmpMonitor across a 70-person distributed workforce.<\/span><\/i><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>Industry:<\/b><span style=\"font-weight: 400\"> IT Services \/ Software Development<\/span><\/p>\n<p><b>Company Size:<\/b><span style=\"font-weight: 400\"> 70 employees\u00a0<\/span><\/p>\n<p><b>Work Model:<\/b><span style=\"font-weight: 400\"> 100% Remote (across 6 countries)\u00a0<\/span><\/p>\n<p><b>Challenge:<\/b><span style=\"font-weight: 400\"> No visibility into productivity, attendance gaps, and rising project delays<\/span><\/p>\n<p><b>Solution:<\/b> <b>EmpMonitor:<\/b><span style=\"font-weight: 400\"> Employee Monitoring &amp; Workforce Productivity Suite Results: 34% productivity increase | 96% attendance accuracy | Project delays down by 38%<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">When our remote team crossed 60 members spread across six countries, we knew our existing tools were no longer enough. Managing a growing, distributed workforce with spreadsheets and weekly check-ins had stopped working months ago.<\/span><\/p>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">This is a first-person account of what actually happened, the good, the difficult, and the genuinely surprising, after we implemented EmpMonitor across our entire operation. We did not know what to expect going in. What we found changed the way we think about managing distributed work entirely.<\/span><\/p>\n<h2><b>The Background: A Remote-First Company With a Visibility Problem<\/b><\/h2>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">We built our company as remote-first from day one. No offices, no commutes, just talented people working from home offices, co-working spaces, and occasionally different time zones. For the first couple of years, it worked well. The team was small, communication was tight, and everyone knew their role.<\/span><\/p>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">But when our remote team scaled past 50 people, the informal systems started to crack. Project managers were spending more time chasing updates than actually managing work. HR had no clean way to verify attendance. Leadership was making decisions based on assumptions rather than data.<\/span><\/p>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">We needed a solution built specifically for remote team management, one that gave us structure without turning us into a surveillance operation.<\/span><\/p>\n<h2><b>The Problem: Three Things We Could Not See:<\/b><\/h2>\n<p><a href=\"\/pricing\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" class=\"aligncenter wp-image-25248 size-full\" title=\"The Problem\" src=\"https:\/\/empmonitor.com\/blog\/wp-content\/uploads\/2026\/03\/The-Problem-Three-Things-We-Could-Not-See.webp\" alt=\"the-problem-remote-team\" width=\"1024\" height=\"576\" srcset=\"https:\/\/empmonitor.com\/blog\/wp-content\/uploads\/2026\/03\/The-Problem-Three-Things-We-Could-Not-See.webp 1024w, https:\/\/empmonitor.com\/blog\/wp-content\/uploads\/2026\/03\/The-Problem-Three-Things-We-Could-Not-See-300x169.webp 300w, https:\/\/empmonitor.com\/blog\/wp-content\/uploads\/2026\/03\/The-Problem-Three-Things-We-Could-Not-See-768x432.webp 768w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/a><\/p>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">Before implementing EmpMonitor, our remote team was operating largely on trust and self-reporting. That worked when everyone knew each other personally. At scale, it created three persistent problems:<\/span><\/p>\n<ul style=\"text-align: justify\">\n<li style=\"font-weight: 400\"><b>No productivity visibility:<\/b><span style=\"font-weight: 400\"> We had no real way to know whether people were actively working or simply online. Task completion rates told us some of the story, but never enough to act on.<\/span><\/li>\n<li style=\"font-weight: 400\"><b>Attendance was unreliable:<\/b><span style=\"font-weight: 400\"> We used an honor-based check-in system. By the time payroll came around, discrepancies between reported and actual hours were frustratingly common.<\/span><\/li>\n<li style=\"font-weight: 400\"><b>Project delays were increasing:<\/b><span style=\"font-weight: 400\"> Missed handoffs, unclear workload distribution, and zero idle-time data meant bottlenecks built up silently until they became full project delays.<\/span><\/li>\n<\/ul>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">These were not problems caused by bad employees. There were systemic gaps that naturally emerge when a remote team grows without the right monitoring infrastructure in place.<\/span><\/p>\n<h2><b>The Discovery: Finding EmpMonitor:<\/b><\/h2>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">We evaluated four platforms before settling on EmpMonitor. What set it apart was not just the feature list; it was the approach. EmpMonitor is built around remote workforce monitoring that gives managers real data without creating a culture of suspicion.<\/span><\/p>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">The features that stood out immediately:<\/span><\/p>\n<ul style=\"text-align: justify\">\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Real-time dashboard with live employee activity status<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Automated attendance tracking with verified clock-in and clock-out<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">URL and application usage monitoring<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Productivity scoring for individuals and teams<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Screenshot monitoring, triggered on demand or automatically<\/span><\/li>\n<li style=\"font-weight: 400\"><span style=\"font-weight: 400\">Insider threat prevention for data security<\/span><\/li>\n<\/ul>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">The platform supported Windows, Mac, and Linux, which mattered for our remote team that uses a mixed device environment. Pricing was straightforward and scalable with no hidden fees as we grew.<\/span><\/p>\n<h2><b>The Implementation: Honesty Made It Work:<\/b><\/h2>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">We have seen other companies bungle monitoring rollouts by treating them as a top-down decision. We took a different approach. Before installing anything, we told our remote team exactly what we were doing and why.<\/span><\/p>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">We hosted a live all-hands call and walked through what EmpMonitor tracks, what it does not track, why we needed it, and how the data would be used.<\/span><\/p>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">The response surprised us. Several team members said they were relieved and frustrated that their effort was invisible and that lower-performing colleagues faced no real accountability. Transparency turned what could have been a trust issue into a genuine trust-builder. Deployment took less than a week. Within 48 hours, the dashboard was live, and the first baselines were coming in.<\/span><\/p>\n<h2><b>What We Saw in the First 30 Days:<\/b><\/h2>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">The first month of remote work tracking data was eye-opening in ways we did not anticipate.<\/span><\/p>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">Our remote team averaged 4.6 hours of active, productive work per eight-hour day. That number was not shockingly low, but now we actually knew it, and we could work with it. URL tracking revealed that a significant portion of working hours was being lost to non-work browsing during core hours. Application monitoring showed excessive context switching between tools, losing productivity not to laziness but to poor workflow design.<\/span><\/p>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">Attendance data also exposed a pattern: employees in certain time zones were logging hours inconsistently, creating payroll reconciliation problems that HR had been quietly absorbing for months. We did not use any of this to punish anyone. We used it to redesign how our remote team worked.<\/span><\/p>\n<h2><b>Month 2: From Observation to Optimization:<\/b><\/h2>\n<p><a href=\"\/pricing\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" class=\"aligncenter wp-image-25247 size-full\" title=\"Observation to Optimization\" src=\"https:\/\/empmonitor.com\/blog\/wp-content\/uploads\/2026\/03\/The-Problem-Three-Things-We-Could-Not-See-1.webp\" alt=\"month-2-from-observation-to-optimization\" width=\"1024\" height=\"576\" srcset=\"https:\/\/empmonitor.com\/blog\/wp-content\/uploads\/2026\/03\/The-Problem-Three-Things-We-Could-Not-See-1.webp 1024w, https:\/\/empmonitor.com\/blog\/wp-content\/uploads\/2026\/03\/The-Problem-Three-Things-We-Could-Not-See-1-300x169.webp 300w, https:\/\/empmonitor.com\/blog\/wp-content\/uploads\/2026\/03\/The-Problem-Three-Things-We-Could-Not-See-1-768x432.webp 768w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/a><\/p>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">With 30 days of baseline data, we made targeted changes across three areas.<\/span><\/p>\n<ol style=\"text-align: justify\">\n<li><b> Workflow redesign:<\/b><span style=\"font-weight: 400\"> We identified the top three tools causing excessive context-switching and consolidated our stack. Average active time climbed from 4.6 to 5.9 hours within three weeks.<\/span><\/li>\n<li><b> Workload rebalancing:<\/b><span style=\"font-weight: 400\"> EmpMonitor&#8217;s individual reports made it clear that two senior developers were absorbing a disproportionate share of urgent tasks. We redistributed responsibilities, and the quality of their output improved noticeably.<\/span><\/li>\n<li><b> Attendance standardization:<\/b><span style=\"font-weight: 400\"> We set clear core-hour expectations per time zone and used EmpMonitor&#8217;s automated tracking to enforce them consistently. Payroll disputes dropped to near zero within the first full payroll cycle.<\/span><\/li>\n<\/ol>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">Our remote team did not just become more productive; it became more fairly managed. And that made a measurable difference to morale.<\/span><\/p>\n<h2><b>The Results: 90 Days Later<\/b><\/h2>\n<table style=\"width: 718px\">\n<tbody>\n<tr>\n<td style=\"width: 338.479px\">\n<p style=\"text-align: center\"><b>Metric<\/b><\/p>\n<\/td>\n<td style=\"width: 365.521px\">\n<p style=\"text-align: center\"><b>Result<\/b><\/p>\n<\/td>\n<\/tr>\n<tr>\n<td style=\"width: 338.479px\"><span style=\"font-weight: 400\">Productivity Increase<\/span><\/td>\n<td style=\"width: 365.521px\">\n<p style=\"text-align: center\"><span style=\"font-weight: 400\">34%<\/span><\/p>\n<\/td>\n<\/tr>\n<tr>\n<td style=\"width: 338.479px\">\n<p style=\"text-align: left\"><span style=\"font-weight: 400\">Attendance Accuracy<\/span><\/p>\n<\/td>\n<td style=\"width: 365.521px\">\n<p style=\"text-align: center\"><span style=\"font-weight: 400\">96%<\/span><\/p>\n<\/td>\n<\/tr>\n<tr>\n<td style=\"width: 338.479px\"><span style=\"font-weight: 400\">Project Delays Reduced<\/span><\/td>\n<td style=\"width: 365.521px\">\n<p style=\"text-align: center\"><span style=\"font-weight: 400\">38%<\/span><\/p>\n<\/td>\n<\/tr>\n<tr>\n<td style=\"width: 338.479px\"><span style=\"font-weight: 400\">Payroll Disputes<\/span><\/td>\n<td style=\"width: 365.521px\">\n<p style=\"text-align: center\"><span style=\"font-weight: 400\">Near Zero<\/span><\/p>\n<\/td>\n<\/tr>\n<tr>\n<td style=\"width: 338.479px\"><span style=\"font-weight: 400\">HR Hours Saved Monthly<\/span><\/td>\n<td style=\"width: 365.521px\">\n<p style=\"text-align: center\"><span style=\"font-weight: 400\">22 hrs<\/span><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">The numbers reflected something deeper than efficiency gains. Our remote team had more clarity about expectations, more confidence that their effort was visible, and more trust in how performance was being measured.<\/span><\/p>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">Project delivery tightened significantly. The 38% reduction in delays came not from pressure, but from better data; managers could now spot a bottleneck forming before it became a crisis. One result we genuinely did not expect: employee satisfaction scores went up. The structure EmpMonitor provided made people feel more supported, not more watched.<\/span><\/p>\n<h2><b>EmpMonitor Features That Drove the Change:<\/b><\/h2>\n<p><a href=\"https:\/\/empmonitor.com\/\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" class=\"aligncenter wp-image-21253 size-full\" title=\"EmpMonitor\" src=\"https:\/\/empmonitor.com\/blog\/wp-content\/uploads\/2025\/08\/EmpMonitor.webp\" alt=\"empmonitor\" width=\"1600\" height=\"900\" srcset=\"https:\/\/empmonitor.com\/blog\/wp-content\/uploads\/2025\/08\/EmpMonitor.webp 1600w, https:\/\/empmonitor.com\/blog\/wp-content\/uploads\/2025\/08\/EmpMonitor-300x169.webp 300w, https:\/\/empmonitor.com\/blog\/wp-content\/uploads\/2025\/08\/EmpMonitor-1024x576.webp 1024w, https:\/\/empmonitor.com\/blog\/wp-content\/uploads\/2025\/08\/EmpMonitor-768x432.webp 768w, https:\/\/empmonitor.com\/blog\/wp-content\/uploads\/2025\/08\/EmpMonitor-1536x864.webp 1536w, https:\/\/empmonitor.com\/blog\/wp-content\/uploads\/2025\/08\/EmpMonitor-1080x608.webp 1080w\" sizes=\"(max-width: 1600px) 100vw, 1600px\" \/><\/a><\/p>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">The feature that made the biggest impact in <\/span><b>EmpMonitor<\/b><span style=\"font-weight: 400\"> was its <\/span><b>activity tracking with productivity insights<\/b><span style=\"font-weight: 400\">. It gave the company a clear view of active vs. idle time and how employees spent their hours across apps and websites. This helped uncover real issues like context switching, non-work browsing, and uneven workloads, not as assumptions, but as actionable data.<\/span><\/p>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">With this clarity, the team could redesign workflows, rebalance tasks, and standardize attendance, leading to measurable gains in productivity and fairness. Supporting features like application tracking and automated reports helped, but it was this core visibility that enabled smarter, data-driven decisions.<\/span><\/p>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">Alongside this, <\/span><b>EmpMonitor&#8217;s<\/b><span style=\"font-weight: 400\"> other supporting features helped strengthen the results:<\/span><\/p>\n<ul style=\"text-align: justify\">\n<li style=\"font-weight: 400\"><b>Application &amp; URL tracking:<\/b><span style=\"font-weight: 400\"> Identified distractions and optimized tool usage.<\/span><\/li>\n<li style=\"font-weight: 400\"><b>Attendance monitoring:<\/b><span style=\"font-weight: 400\"> Ensured consistent work hours across time zones.<\/span><\/li>\n<li style=\"font-weight: 400\"><b>Automated reports &amp; dashboards:<\/b><span style=\"font-weight: 400\"> Enabled quick insights and faster decision-making.<\/span><\/li>\n<li style=\"font-weight: 400\"><b>Individual performance reports:<\/b><span style=\"font-weight: 400\"> Helped balance workloads more fairly.<\/span><\/li>\n<\/ul>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">These features supported the core activity tracking by turning insights into consistent improvements.<\/span><\/p>\n<h2><b>What We Would Tell Other Remote-First Companies?<\/b><\/h2>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">If your remote team has grown past 20 people and you are still relying on self-reporting and trust alone, you are probably operating with a significant visibility gap, and you likely do not know how large it is.<\/span><\/p>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">EmpMonitor did not fix our people problems. It revealed that most of what we thought were people problems were actually process and visibility problems. That distinction matters enormously.<\/span><\/p>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">The tool works best when you lead with transparency, use the data for improvement rather than punishment, and treat your remote team as partners in the process. Done right, monitoring does not erode trust; it actively builds it.<\/span><\/p>\n<h2><b>The Takeaway:<\/b><\/h2>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">Scaling a remote team without the right infrastructure is like navigating without a map. You might reach your destination eventually, but you will take a lot of costly wrong turns along the way.<\/span><\/p>\n<p style=\"text-align: justify\"><span style=\"font-weight: 400\">EmpMonitor gave us the map. It showed us where time was going, who was carrying too much weight, and where our systems were letting good people down. The result was a more productive, more fairly managed, and genuinely happier team and a leadership group that could finally make decisions based on data rather than assumptions.<\/span><\/p>\n<h2><b>FAQ\u2019s:<\/b><\/h2>\n<p style=\"text-align: justify\"><b>Q1. Is EmpMonitor suitable for fully remote or hybrid teams?<\/b><\/p>\n<p style=\"text-align: justify\"><b>Ans:<\/b><span style=\"font-weight: 400\"> Yes. EmpMonitor is designed for distributed teams, offering cross-platform support (Windows, Mac, etc.) and a real-time dashboard that works from anywhere. It helps managers track productivity, attendance, and workflows without needing a physical office setup.<\/span><\/p>\n<p style=\"text-align: justify\"><b>Q2. Does employee monitoring reduce trust or harm team morale?<\/b><\/p>\n<p style=\"text-align: justify\"><b>Ans:<\/b><span style=\"font-weight: 400\"> Not if implemented transparently. When employees understand what is being tracked and why, monitoring often improves fairness. It ensures high performers are recognized and workloads are balanced, which can actually boost morale and accountability.<\/span><\/p>\n<p style=\"text-align: justify\"><b>Q3. How quickly can EmpMonitor be set up and start showing results?<\/b><\/p>\n<p style=\"text-align: justify\"><b>Ans:<\/b><span style=\"font-weight: 400\"> Deployment is fast and straightforward. Most teams can be onboarded within a week, with initial data and insights available within 24\u201348 hours. Meaningful improvements in productivity and workflow can often be seen within the first 30 days.<\/span><\/p>\n<p style=\"text-align: justify\"><b>Q4. What kind of data does EmpMonitor track?<\/b><\/p>\n<p style=\"text-align: justify\"><b>Ans:<\/b><span style=\"font-weight: 400\"> EmpMonitor tracks active vs. idle time, application and website usage, attendance, and overall productivity trends. It focuses on work-related insights rather than intrusive monitoring, helping teams improve efficiency without micromanagement.<\/span><\/p>\n<p style=\"text-align: justify\"><b>Q5. Is EmpMonitor legal and compliant with privacy regulations?<\/b><\/p>\n<p style=\"text-align: justify\"><b>Ans:<\/b><span style=\"font-weight: 400\"> Yes, when used responsibly. EmpMonitor is designed to support transparent monitoring practices. Companies should inform employees, define clear policies, and ensure compliance with local labor and data privacy laws for ethical use.<\/span><\/p>\n<p><a href=\"https:\/\/empmonitor.com\/\" target=\"_blank\" rel=\"noopener\"><img decoding=\"async\" class=\"aligncenter wp-image-14440 size-full\" title=\"EmpMonitor\" src=\"https:\/\/empmonitor.com\/blog\/wp-content\/uploads\/2024\/04\/EmpMonitor-1.webp\" alt=\"empmonitor-banner\" width=\"1024\" height=\"576\" srcset=\"https:\/\/empmonitor.com\/blog\/wp-content\/uploads\/2024\/04\/EmpMonitor-1.webp 1024w, https:\/\/empmonitor.com\/blog\/wp-content\/uploads\/2024\/04\/EmpMonitor-1-300x169.webp 300w, https:\/\/empmonitor.com\/blog\/wp-content\/uploads\/2024\/04\/EmpMonitor-1-768x432.webp 768w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>A first-person account of what actually changed, in productivity, accountability, and team morale, after rolling out EmpMonitor across a 70-person distributed workforce. Industry: IT Services \/ Software Development Company Size: 70 employees\u00a0 Work Model: 100% Remote (across 6 countries)\u00a0 Challenge: No visibility into productivity, attendance gaps, and rising project delays Solution: EmpMonitor: Employee Monitoring &amp; [&hellip;]<\/p>\n","protected":false},"author":46,"featured_media":25249,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[2488,1652,1630],"tags":[389,2754,4206],"class_list":["post-25236","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-employee-evaluation","category-workforce-analytics-software","category-workforce-management-tools","tag-remote-team-management","tag-remote-workforce-monitoring","tag-remote-work-tracking","et-has-post-format-content","et_post_format-et-post-format-standard"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/empmonitor.com\/blog\/wp-json\/wp\/v2\/posts\/25236","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/empmonitor.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/empmonitor.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/empmonitor.com\/blog\/wp-json\/wp\/v2\/users\/46"}],"replies":[{"embeddable":true,"href":"https:\/\/empmonitor.com\/blog\/wp-json\/wp\/v2\/comments?post=25236"}],"version-history":[{"count":3,"href":"https:\/\/empmonitor.com\/blog\/wp-json\/wp\/v2\/posts\/25236\/revisions"}],"predecessor-version":[{"id":25254,"href":"https:\/\/empmonitor.com\/blog\/wp-json\/wp\/v2\/posts\/25236\/revisions\/25254"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/empmonitor.com\/blog\/wp-json\/wp\/v2\/media\/25249"}],"wp:attachment":[{"href":"https:\/\/empmonitor.com\/blog\/wp-json\/wp\/v2\/media?parent=25236"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/empmonitor.com\/blog\/wp-json\/wp\/v2\/categories?post=25236"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/empmonitor.com\/blog\/wp-json\/wp\/v2\/tags?post=25236"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}